issue-tracker
/issue-tracker
File, update, and close GitHub work as one epic with native sub-issues. Use when the user asks to file, track, update, or close a GitHub issue, or to open, update, or refresh an epic and its sub-issues.
- Author
- jl-cmd-projects ↗
- Repository
- claude-dev-env ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 4
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (4). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
File, update, and close GitHub work as one epic with native sub-issues. Use when the user asks to file, track, update, or close a GitHub issue, or to open, update, or refresh an epic and its sub-issues.
Arguments
/issue-tracker [issue action - file | update | close | refresh-epic | full handoff]
Original author description
File, update, and close GitHub work as one epic with native sub-issues. Use when the user asks to file, track, update, or close a GitHub issue, or to open, update, or refresh an epic and its sub-issues.
How it works
- Voice
- Gotchas
- The model
- Labels
- Markers
- Dedup
- Tools
- Handoff input
- Close the sub-issue through the PR (required when a fix ships)
- Return shape
SKILL.md preview
--- name: issue-tracker description: >- File, update, and close GitHub work as one epic with native sub-issues. Use when the user asks to file, track, update, or close a GitHub issue, or to open, update, or refresh an epic and its sub-issues. argument-hint: "[issue action - file | update | close | refresh-epic | full handoff]" --- # Issue tracker **User wants an issue action done. Here is how those actions work.** **dedup -> do the work -> markers only -> numbers + URLs** Run every step the ask needs in one go (file, label, attach, refresh, and so on). Prefer the **same warm** `pstack:poteto-agent` for follow-ups on the same issue or a related issue on the same epic. Spawn a new agent only for an unrelated work-stream or when the warm agent is gone. ## Voice End with the issue number(s) and URL(s) the caller must keep, and nothing else. ## Gotchas Append a bullet when an action fails in a new way. - Use REST `.id`, not display `#N`, to attach a sub-issue - [operation-matrix](reference/operation-matrix.md). - `gh` attach: `-F sub_issue_id=<n>` (typed int), never `-f`. - Status goes in markers, not comments - comments are cross-links only. - Dedup open **and** closed; closed twin -> reopen vs file new, never silent refile. - Edit only between markers - free-form epic edits break the children checklist. - Auto-close is PR-body-first: a related-only UI link does not close the issue on merge. ## The model One **epic** issue owns a work-stream. Each unit of work is a native GitHub **sub-issue** under it. The epic checklist and every status block live inside marker pairs. Skeletons and refresh steps: [reference/epic-and-sub-issue-model.md](reference/epic-and-sub-issue-model.md). ## Labels - Parent: `epic`. - Sub-issue: `type: roadblock`, `type: task`, `type: bug`, or `type: enhancement`. Create a missing label, then apply it. Label create is in the operation matrix. ## Markers - Status (any issue): `<!-- issue-tracker:status -->` … `<!-- /issue-tracker:status -->` - Children checklist (epic only): `<!-- issue-tracker:children -->` … `<!-- /issue-tracker:children -->` Update path: read body -> replace only the text between the target pair -> write the full body back. ## Dedup Search open and closed issues on the target repo before create. Open twin -> update in place. Closed twin -> ask reopen vs file new. ## Tools Prefer GitHub MCP. Fall back to `gh` on the same REST endpoints. Full map and `.id` rule: [reference/operation-matrix.md](reference/operation-matrix.md). Before issue creation, a full issue body edit, or an issue comment, write the body to a UTF-8 file. Resolve the active managed root (`CLAUDE_CONFIG_DIR` when set, `~/.claude` otherwise), then run `<managed-root>/scripts/durable_post_lint.py`. Use `issue-create`, `issue-edit`, or `issue-comment` as the action. Send the server write only after exit code `0`. ## Handoff input Optional issue-candidate JSON from orchestrator or closeout. Full schema and consume path: [reference/handoff-schema.md](reference/handoff-schema.md). ## Close the sub-issue through the PR (required when a fix ships) GitHub closes the sub-issue when someone **merges** a pull request into the **default branch** and that PR carries a closing keyword for the issue. **Required on the PR that merges into the default branch:** put `Closes #N` in the PR body for each finished sub-issue. One keyword per issue: write `Closes #12` and `Closes #13`, not `Closes #12, #13` (only the first number closes in the comma form). **Preferred on commits:** also put `Closes #N` in the first commit message when the fix starts. Commit alone is backup; the PR body is the contract. **Stacked / intermediate PRs** that do not merge into the default branch: use a plain `#N` reference in the body so the issue links without a false close promise. Put `Closes #N` only on the PR that lands on the default branch. **Not enough:** a Development "related" link with no closing keyword. **Not enough:** closing the PR without merging. **A defect found while working the issue stays on the issue.** Keep the issue open and fix the defect through this issue's pull request. A close that routes the defect to another issue or epic leaves the work unfinished, and `hooks/blocking/issue_close_handoff_gate.py` denies it. **Who owns `#N`:** the agent or session writing the PR must use the correct sub-issue number. Nothing in this package verifies the number matches the fix. ## Return shape Reply with every affected issue number and URL - no narration after that payload. ## File index | File | Purpose | |------|---------| | `SKILL.md` | Hub: how issue actions work, gotchas, model, markers, dedup, PR auto-close, return shape | | `reference/operation-matrix.md` | MCP + `gh` per action; sub-issue `.id` rule | | `reference/epic-and-sub-issue-model.md` | Epic model, markers, body skeleton, checklist refresh | | `reference/handoff-schema.md` | Issue-candidate JSON and consume flow |
Files in this package (4)
- SKILL.md 5 KB
- reference/epic-and-sub-issue-model.md 2 KB
- reference/handoff-schema.md 3 KB
- reference/operation-matrix.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jl-cmd-projects/claude-dev-env | 90 | MIT |
| DvJ4Y/shipwright | 100 | MIT |
Database snapshot: 13.11.2026 · package version 62651f0ed598 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100issue
Use when creating or opening a GitHub issue, including tracker and child issues, or several issues at once. - 100dx-create-epic
Use when you need to create a GitHub issue for an epic: one outcome too large for a single story, delivered by several stories and chores that link to it as native sub-issues. Triggers on "create an epic", "file an epic for this", "group these issues under an epic", and "make… - 100issue-tracking
Create, manage, and track issues in GitHub, Linear, or GitLab. Use when the user asks to "create an issue", "file a bug", "check issues", "update a ticket", "create an epic", or anything about issue/ticket management. - 100github-issues
Administers company work on the GitHub Project \"Dezkareid Enterprise\": create, update, assign, prioritize, move status, close or delete issues and epics, attach sub-issues to epics, and categorize every issue with Conventional Commits types. Use this skill whenever the user… - 90github-issues
View, create, comment on, label, assign, close, reopen and work on GitHub issues of the current repository with the gh CLI, including their type, fields, projects, milestone, relationships (parent, sub-issues, blocked by) and linked branches. Use when the user mentions an issue… - 100nxs-gh-create-epic
Create a GitHub issue from an Epic document. Use when the user wants to create a GitHub issue from an epic.md file, sync an epic to GitHub, or link an epic document to a GitHub issue. The skill extracts the epic title and type from YAML frontmatter, creates an issue via `gh…