Agent skill · mia-cx

address-issue

Use when the user asks to address or implement an issue.

What it needs

About 2k tokens when loaded.

What this skill does

Address issue Implement a provided issue in the harness- or user-supplied workspace and Git context. Core loop: plan → atomic TODOs → one commit per TODO → PR (or comment+close when no code change). Workflow 1. Identify the issue and repo state Parse the issue number or URL; ask only if ambiguous. Harness-supplied repo root, worktree, branch, and base are authoritative; change them only on explicit user request. Do not relocate the task to dodge a dirty tree. From that root: If the issue is closed, stop unless the user asked to reopen or work closed issues. If uncommitted changes exist outside .plans/, ask how to handle them before mixing work. 2. Read, understand, and draft the plan Read the issue body and relevant code first. Search for existing patterns, tests, and conventions. If no code change is warranted (question, duplicate, already fixed, works-as-intended): post findings as an issue comment, close with gh issue close <n> --reason "not planned" or completed, and stop. No branch, no PR. When plans are part of the repo's conventions, create/update .plans/<number>-<slug>.md: TODO rules: each independently committable; include tests/validation as TODOs; prefer 3–8; split vague ones before coding; unclear requirements → Notes + ask before coding. Commit the initial plan only when that is normal for the repo. If .plans/ is ignored or local-only, keep it updated without committing. 3. Execute one TODO at a time For each TODO: 1. Mark in progress (- [~]) or note it under Notes. 2. Smallest change that completes it. 3. Focused validation for that TODO. 4. Mark complete (- [x]), record validation, revise TODOs on discovery. 5. Commit before the next TODO: One completed TODO per commit (or per split item). Keep commits buildable. Refs #<n> on intermediate commits; Closes #<n> only on the final implementation commit or PR body when the issue is fully resolved. 4. Final validation After all TODOs: On failure: diagnose, fix, or record residual risk before filing the PR. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills mia-cx/address-issue

View the source on GitHub

Browse the @skills marketplace