issuelisted

# Issue ## Pick the tracker | Tracker | When | Template | | --- | --- | --- | | GitHub | The repo has a GitHub remote and the branch carries no project key | `templates/github-bug.md`, `templates/github-feature.md` | | Jira | The branch name or `AGENTS.md` carries a project key such as `KEY-123` | `templates/jira-story.md`, `templates/jira-bug.md`, `templates/jira-epic.md` | When unclear, use `ask`: GitHub or Jira. Do not guess. ## 1. Deduplicate ```bash gh issue list --search "<keywords>" --state all --limit 10 ``` Search Jira with JQL. Comment on a match rather than duplicating it. ## 2. Write Use the matching template and fill every placeholder: - GitHub: `github-bug.md` or `github-feature.md`. - Jira: story, bug, or epic template. Title: imperative, under 72 characters, no period. Bugs need version, steps, expected and actual results. Features lead with the problem. ## 3. Read valid values Never invent values. Use `gh label list`, `list_issue_types`, and `list_issue_fields`. ## 4. Classify Set the type first: Bug for something that broke or contradicts its documentation, Feature for new behavior somebody asked for, Task for work with no user-visible change, such as CI, releases, or agent files. When the type is not obvious, follow the `ask` skill: Bug, Feature, Task. Do not guess Medium/Medium and move on. | Field | Options | Pick | | --- | --- | --- | | Priority | Urgent, High, Medium, Low | Urgent blocks a release or breaks the published package for every