
Address Issue
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Fetch a GitHub issue, plan the work, execute the changes, and commit with issue references.
About
Address-issue fetches a GitHub issue, plans the work it implies, executes the code changes, and commits with references back to the issue. It runs the whole loop from a tracked task to committed implementation. A workflow skill for issue-driven development.
- Fetches a GitHub issue
- Plans the work
- Executes code changes
- Commits with issue references
Address Issue by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install address-issue@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Fetch a GitHub issue, plan the work, execute the changes, and commit with issue references.
README.md
Address Issue
Fetch a GitHub issue, analyze it, plan and execute the work in the current branch, and commit with issue references.
Type: Skill
Trigger: /address-issue
Installation
See the marketplace install instructions.
What It Does
Fetches a GitHub issue by number or search text, classifies it (bug fix, feature, documentation, refactor, or chore), extracts sub-tasks from task list checkboxes, plans the work, executes changes, and commits with conventional commit messages that reference the issue number. Marks the issue "in progress" at the start and leaves that label in place until the related PR is merged or the user explicitly abandons the effort.
Usage
/address-issue #42
/address-issue the dark mode issue
/address-issue #42 --dry-run
/address-issue #42 --no-commit
/address-issue #42 --commit-per-change
| Option | Description |
|---|---|
--dry-run |
Fetch, analyze, and plan without making changes |
--no-commit |
Make changes but do not commit them |
--commit-per-change |
Commit after each logical change instead of grouping |
Recommended Permissions
Allow these gh commands so the skill can run without repeated permission prompts:
gh issue view *gh issue list *gh issue edit *gh label create *
Examples
- "address issue #42": fetches the issue, plans the work, makes changes, and commits
- "fix issue #15": same workflow, triggered by a different phrase
- "address #88 --dry-run": shows the plan without making changes
- "address the login bug": searches for the issue by description
See Also
- Create Issue: create new GitHub issues
- Create Worktree from Issue: start an issue in a new worktree instead of the current branch
- Suggest Next Issue: find which issue to work on next
- All plugins