Setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the def…
by helderberto · MIT
The skill
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
Setup
Per repo. Records where every flow skill keeps specs and tickets. No config → markdown under .specs/, the default. GitHub or Jira → only in that tracker. Rerun to switch: new work follows the new choice, nothing migrates.
1. Explore
git remote -v: GitHub remote?.specs/issue-tracker.md: prior output of this skill?git check-ignore -q .specs: already ignored?
2. Ask one question
Argument given (local, github, jira <KEY>) → skip the question. Otherwise: which tracker? Lead with the recommendation: GitHub when the remote is on GitHub, else local.
- GitHub →
ghCLI - Jira → ask the project key; Atlassian MCP
- Local → markdown in
.specs/only
3. Write
Never touch committed files: no AGENTS.md, CLAUDE.md, or .gitignore edits. The skills read the config directly.
Local → remove .specs/issue-tracker.md if present; skills fall back to issue-tracker-local.md. Done.
GitHub / Jira → copy the seed (issue-tracker-github.md or issue-tracker-jira.md) to .specs/issue-tracker.md, filling the placeholders.
.specs/ not ignored → append .specs/ to .git/info/exclude: ignored for this clone, never committed.
GitHub + hitl label missing → gh label create hitl --force.
4. Done
Print the tracker chosen and the files written. Switching later: rerun, or edit .specs/issue-tracker.md.
Next: /hb:triage or /hb:grill <idea>.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: helderberto/setup-71770050352.
Details
- Publisher
- helderberto
- Category
- Software Development › Developer docs & tooling
- License
- MIT
- Updated
- 2026-10-16
References
More from helderberto
- A11Y Audit Audit accessibility (WCAG) in frontend code.
- Architecture Audit Surface architectural friction across a codebase and propose deep-module refactors as RFCs.
- Build Implement the next unblocked ticket test-first and commit it, or fan every ticket out to parallel…
- Check Validate code quality — auto-fix formatting/lint, verify types, run tests.