", "body": "<body>", "type": "Bug", "labels": ["bug"], "issue_fields": [ { "field_name": "Priority", "field_option_name": "High" }, { "field_name": "Effort", "field_option_name": "Medium" } ] } ``` Use `method: "update"` when triaging an existing issue. Report URL and values. ## Jira - Story: persona and independently testable acceptance criteria, one behavior per bullet. - Bug: steps and actual behavior. Epic: goal and related stories. - Split work that cannot fit a sprint. Do not make a one-off fix an epic. - Use `createJiraIssue` / `editJiraIssue`; link ticket references. - Put payloads in fences. Type inline backticks in Jira's editor and verify the result. ## Guardrails - One issue does one thing; split mixed reports. - No tokens, `.env` lines, or internal hostnames in a body. Say where the value lives. - Do not raise Priority to jump a queue. - Run `humanizer` over title and body. ## Related skills | Skill | Use for | | --- | --- | | [pr](../pr/SKILL.md) | The pull request that closes the issue | | [humanizer](../humanizer/SKILL.md) | AI tells in the title and body | | [ask](../ask/SKILL.md) | Picker vs lettered list for tracker and type |

# Issue > Create or triage a GitHub or Jira issue with its type, labels, and fields filled. - Skill: `stijnvanhulle/issue` (Agent Skill, multi-file: 6 files) - Install (CLI): `npx skillmds@latest add stijnvanhulle/issue` - Raw SKILL.md: https://api.skillmd.com/api/skills/stijnvanhulle/issue/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: stijnvanhulle (https://skillmd.com/u/stijnvanhulle) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/stijnvanhulle/issue --- # 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 "" --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 everyone. High hits users today with no workaround. Medium is the default. Low is a nice-to-have | | Effort | High, Medium, Low | Low is one file a reviewer reads in one sitting. Medium spans a few files or needs a test. High needs a design decision or touches a public API | Use `ask` when Priority or Effort remains ambiguous. ## 5. Create Use `gh issue create` for the body and the GitHub MCP `issue_write` for type and fields: ```json { "method": "create", "owner": "", "repo": "", "title": "", "body": "<body>", "type": "Bug", "labels": ["bug"], "issue_fields": [ { "field_name": "Priority", "field_option_name": "High" }, { "field_name": "Effort", "field_option_name": "Medium" } ] } ``` Use `method: "update"` when triaging an existing issue. Report URL and values. ## Jira - Story: persona and independently testable acceptance criteria, one behavior per bullet. - Bug: steps and actual behavior. Epic: goal and related stories. - Split work that cannot fit a sprint. Do not make a one-off fix an epic. - Use `createJiraIssue` / `editJiraIssue`; link ticket references. - Put payloads in fences. Type inline backticks in Jira's editor and verify the result. ## Guardrails - One issue does one thing; split mixed reports. - No tokens, `.env` lines, or internal hostnames in a body. Say where the value lives. - Do not raise Priority to jump a queue. - Run `humanizer` over title and body. ## Related skills | Skill | Use for | | --- | --- | | [pr](../pr/SKILL.md) | The pull request that closes the issue | | [humanizer](../humanizer/SKILL.md) | AI tells in the title and body | | [ask](../ask/SKILL.md) | Picker vs lettered list for tracker and type |