feat(smart-mind-map-tool): initial release v1.0.0 with adaptive Rich UI

.agent/skills/gh-issue-scheduler/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: gh-issue-scheduler
+description: Finds all open GitHub issues that haven't been replied to by the owner, summarizes them, and generates a solution plan. Use when the user wants to audit pending tasks or plan maintenance work.
+---
+
+# Gh Issue Scheduler
+
+## Overview
+
+The `gh-issue-scheduler` skill helps maintainers track community feedback by identifying unaddressed issues and drafting actionable technical plans to resolve them.
+
+## Workflow
+
+1.  **Identify Unanswered Issues**: Run the bundled script to fetch issues without owner replies.
+    *   Command: `bash scripts/find_unanswered.sh`
+2.  **Analyze and Summarize**: For each identified issue, summarize the core problem and the user's intent.
+3.  **Generate Solution Plans**: Draft a technical "Action Plan" for each issue, including:
+    *   **Root Cause Analysis** (if possible)
+    *   **Proposed Fix/Implementation**
+    *   **Verification Strategy**
+4.  **Present to User**: Display a structured report of all pending issues and their respective plans.
+
+## Tool Integration
+
+### Find Unanswered Issues
+```bash
+bash scripts/find_unanswered.sh
+```
+
+## Report Format
+
+When presenting the summary, use the following Markdown structure:
+
+### 📋 Unanswered Issues Audit
+
+#### Issue #[Number]: [Title]
+- **Author**: @username
+- **Summary**: Concise description of the problem.
+- **Action Plan**:
+    1. Step 1 (e.g., Investigate file X)
+    2. Step 2 (e.g., Apply fix Y)
+    3. Verification (e.g., Run test Z)

.agent/skills/gh-issue-scheduler/scripts/find_unanswered.sh

@@ -0,0 +1,42 @@
+#!/usr/bin/env bash
+
+# Fetch all open issues and filter for those without responses from the owner/collaborators.
+# Uses 'gh' CLI.
+
+REPO_FULL=$(gh repo view --json owner,name -q ".owner.login + "/" + .name")
+OWNER=${REPO_FULL%/*}
+
+# 1. Get all open issues
+OPEN_ISSUES=$(gh issue list --state open --json number,title,author,createdAt --limit 100)
+
+echo "Analysis for repository: $REPO_FULL"
+echo "------------------------------------"
+
+# Process each issue
+echo "$OPEN_ISSUES" | jq -c '.[]' | while read -r issue; do
+    NUMBER=$(echo "$issue" | jq -r '.number')
+    TITLE=$(echo "$issue" | jq -r '.title')
+    AUTHOR=$(echo "$issue" | jq -r '.author.login')
+    
+    # Check comments for owner responses
+    # We look for comments where the author is the repo owner
+    COMMENTS=$(gh issue view "$NUMBER" --json comments -q ".comments[].author.login" 2>/dev/null)
+    
+    HAS_OWNER_REPLY=false
+    for COMMENT_AUTHOR in $COMMENTS; do
+        if [ "$COMMENT_AUTHOR" == "$OWNER" ]; then
+            HAS_OWNER_REPLY=true
+            break
+        fi
+    done
+    
+    if [ "$HAS_OWNER_REPLY" == "false" ]; then
+        echo "ISSUE_START"
+        echo "ID: $NUMBER"
+        echo "Title: $TITLE"
+        echo "Author: $AUTHOR"
+        echo "Description:"
+        gh issue view "$NUMBER" --json body -q ".body"
+        echo "ISSUE_END"
+    fi
+done