# Setup

> Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the def…

Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).

- Page: https://ss33.ai/skills/helderberto/setup-71770050352
- Publisher: helderberto
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Developer docs & tooling](https://ss33.ai/skills/category/software-development-t44z8z/developer-docs-and-tooling-nich6w)
- License: MIT
- Source: https://github.com/helderberto/agent-skills/blob/445681fd215e649201f91d65492025f0803efc0a/skills/setup/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/helderberto/setup-71770050352

# 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** → `gh` CLI
- **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](issue-tracker-local.md). Done.

**GitHub / Jira** → copy the seed ([issue-tracker-github.md](issue-tracker-github.md) or [issue-tracker-jira.md](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>`.