メニュー
Interactive issue review and grooming session. Pulls all issues for the current project and walks through them with the user to triage, update, resolve, or archive. Use when grooming a backlog, reviewing open issues, or cleaning up stale tasks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design electronic schematics and PCB netlists from Pi using SKiDL. Use for circuit creation, KiCad library parts, nets/buses, ERC, BOMs, SVG schematics, KiCad schematic export, and standalone SKiDL Python.
CAD modeling with build123d from Pi. Use when creating, inspecting, rendering, or exporting parametric 3D models, STL files, STEP files, enclosures, brackets, and other mechanical parts.
Schedule one-time or recurring agent jobs from Pi. Use when the user asks for cron-like reminders, recurring checks, scheduled prompts, or inspecting/completing scheduled jobs.
Track and manage issues using the dude MCP server. List, create, update issues. Track bugs, tasks, blockers, and problems within projects. Search for issues. Use when tracking bugs, creating tasks, managing blockers, recording problems, or working with issue hierarchies.
Manage development projects using the dude MCP server. List projects, view records by project, search across projects. Projects are auto-detected from git — no manual creation needed. Use when exploring project organization, starting work on a codebase, or needing project-level context.
Interactive specification review session. Pulls all specs and architecture decisions for the current project and walks through them with the user to verify accuracy, update, or archive. Use when reviewing technical documentation, validating architecture decisions, or cleaning up outdated specs.
| name | review-issues |
| description | Interactive issue review and grooming session. Pulls all issues for the current project and walks through them with the user to triage, update, resolve, or archive. Use when grooming a backlog, reviewing open issues, or cleaning up stale tasks. |
Walk through all issues for the current project with the user.
When this skill is invoked, follow these steps in order:
Call these in parallel:
dude_list_records { "kind": "issue", "status": "open" }
dude_list_records { "kind": "issue", "status": "resolved" }
Show the user a summary of what exists:
For each open issue, present it and ask the user:
Apply changes immediately using:
dude_upsert_record { "id": <issue_id>, "kind": "issue", "title": "<updated_title>", "status": "<new_status>" }
Ask the user if they want to review recently resolved issues. If yes, walk through them and ask:
Ask the user if there are any new issues to capture. If yes, create them:
dude_upsert_record { "kind": "issue", "title": "TASK: <description>", "body": "<details>" }
Present a final summary of all changes made during the session:
| Tool | Purpose |
|---|---|
dude_list_records | Fetch issues by kind and status |
dude_upsert_record | Update or create issues |
dude_search | Find related issues if needed |