メニュー
Use when user wants to Scan the repo for TODO code comments, TODO-titled GitHub issues, and predict the next best work item to tackle. Reusable across any git repository.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when user wants to Coding patterns and conventions extracted from the Win dotfiles repository. Covers commit style, PowerShell script structure, file organization, CI behavior, and issue tracking. Load when writing scripts, commits, or docs for this repo.
Use when the user wants to commit local changes, sync with GitHub, and push. Triggers on "merge my changes", "push to remote", "commit and push", "merge into main", "sync local changes", "get my changes onto main", or any request to integrate local/branch work into main and push to GitHub.
Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows. Use when an agent needs to install, verify, troubleshoot, configure, or operate Open Computer Use through its native CLI, stdio MCP server, or direct Computer Use tool calls.
Orchestrates repository and file system cleanup through sequential phases: separating code from docs, organizing folder structure (both repos and general directories), removing legacy code, removing script clutter, pruning documentation sprawl, cleaning documentation content (emojis, hyperbole, 'comprehensive'), and eliminating duplicate files. Use when cleaning repositories, organizing projects, removing legacy code, pruning AI-generated docs, organizing Downloads/Documents/project folders, finding duplicates, restructuring folder hierarchies, or establishing organizational systems. Triggers on: 'clean up repo', 'janitor', 'organize', 'repository cleanup', 'remove legacy', 'prune docs', 'find duplicates', 'organize folder', 'project structure', 'tidy workspace', 'folder cleanup', 'downloads organization'.
Use whenever the user wants Claude to connect to, inspect, run commands on, or move files to/from a device on the local network via SSH - a Raspberry Pi, home server, NAS, router, or any other LAN box, whether referenced by a ~/.ssh/config alias, a raw IP (e.g. 192.168.1.x), or a hostname like "the pi" / "my nas" / "the server in the closet". Also use for discovering what's alive on the LAN, setting up key-based auth to a new device, or running the same check across several LAN hosts. Trigger even if the user doesn't say "SSH" explicitly - e.g. "restart the service on the pi", "grab the logs off my nas", "what's running on 192.168.1.50", "copy this file to my server".
Transforms complex projects into clear, actionable plans through design exploration and strategic breakdown. Guides design validation before implementation, decomposes features into atomic tasks, maps dependencies and critical paths, assesses risks, estimates effort and timeline. Use for new features, refactoring, migrations, team scaling, complex debugging. Provides both design options and implementation roadmaps.
| name | todo-scan |
| description | Use when user wants to Scan the repo for TODO code comments, TODO-titled GitHub issues, and predict the next best work item to tackle. Reusable across any git repository. |
You are performing a structured triage of outstanding work for the current repository. Execute all three phases, then synthesize a recommendation.
Find all TODO/FIXME/HACK/XXX annotations in tracked source files:
REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
cd "$REPO_ROOT"
# Search source files, exclude common noise dirs
git grep -n --no-color -E "(TODO|FIXME|HACK|XXX)\b" \
-- ':!*.lock' ':!node_modules' ':!.git' ':!dist' ':!build' ':!__pycache__' ':!*.min.js' \
2>/dev/null | head -80
Group results by file. For each TODO, note:
Check if the gh CLI is available and the repo has a GitHub remote:
GH_REMOTE=$(git remote -v 2>/dev/null | grep -oP '(?<=github.com[/:])[^/]+/[^\s.]+' | head -1)
if command -v gh >/dev/null 2>&1 && [ -n "$GH_REMOTE" ]; then
echo "=== Open issues with TODO in title ==="
gh issue list --search "TODO in:title" --state open --limit 20
--json number,title,labels,assignees,createdAt
--jq '.[] | "#(.number) [(.labels | map(.name) | join(", "))] (.title)"' 2>/dev/null ||
gh issue list --search "TODO in:title" --state open --limit 20 2>/dev/null
echo ""
echo "=== Open issues with FIXME in title ==="
gh issue list --search "FIXME in:title" --state open --limit 10
--json number,title --jq '.[] | "#(.number) (.title)"' 2>/dev/null
else
echo "gh CLI not available or no GitHub remote detected. Skipping issue search."
echo "Remote detected: ${GH_REMOTE:-none}"
fi
Gather signals about recent activity and open work:
echo "=== Recent commits (last 10) ===" git log --oneline -10 2>/dev/null
echo "=== Uncommitted changes ===" git status --short 2>/dev/null
echo "=== Most-changed files (last 30 days) ==="
git log --since="30 days ago" --name-only --format="" 2>/dev/null |
grep -v '^$' | sort | uniq -c | sort -rn | head -15
echo "=== Open PRs (if gh available) ==="
command -v gh >/dev/null 2>&1 &&
gh pr list --state open --limit 10
--json number,title,isDraft
--jq '.[] | "#(.number)(if .isDraft then " [DRAFT]" else "" end) (.title)"' 2>/dev/null ||
echo "gh not available"
echo "=== Failed CI on recent commits (if gh available) ==="
gh run list --limit 5 --json conclusion,name,headBranch
--jq '.[] | select(.conclusion == "failure") | "(.name) on (.headBranch)"' 2>/dev/null || \
After collecting all three phases of data, reason through the following and produce a structured report:
List all code TODOs grouped by severity:
List any GitHub issues found, noting if they overlap with code TODOs.
Apply this heuristic to pick the single best next item:
Output format:
FILE:LINE - TODO_TEXT Reason: 1-2 sentence explanation using signals above
Alternatives:
gh is unavailable, Phases 2 and CI checks are skipped gracefullyhead -80 limit in Phase 1 for very large repos/todo-scan or ask Claude to "scan todos and predict next step"