Generate Test Plan
openshift-eng/ai-helpers
Generate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both.
Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask.
Install Bug Retest Triage
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bug-retest-triage .claude/skills/bug-retest-triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .claude/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/bug-retest-triage .agents/skills/bug-retest-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .agents/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/bug-retest-triage .cursor/skills/bug-retest-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .cursor/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mirumee/nimara-ecommerce.git --path .claude/skills/bug-retest-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/bug-retest-triage .gemini/skills/bug-retest-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .gemini/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/bug-retest-triage .github/skills/bug-retest-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .github/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mirumee/nimara-ecommerce bug-retest-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/bug-retest-triage .opencode/skills/bug-retest-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bug-retest-triage" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/.claude/skills/bug-retest-triage into .opencode/skills/bug-retest-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-retest-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
bug-retest-triage- GitHub stars
- 129
- Token cost
- ~888 tokens
- SKILL.md length
- 377 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask.
- Works in 4 steps: Evidence only. A verdict requires an… → Never fabricate. Missing repro steps,… → One ticket at a time, on a shared board.… → …
- The user asks to retest
- SKILL.md covers Operating principles, Before you start, Workflow (per ticket) and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bug Retest Triage is an agent skill from mirumee/nimara-ecommerce. Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask. Use this skill whenever the user asks to retest, re-verify, triage, or work through reported bugs/tickets one at a time; to "run the Phase 2 flow"; to pick the next ticket off the To Do column; or to confirm whether a fix holds. Works one ticket at a time on a board shared with human QA. Do NOT use for designing new test…
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test generation. It works with Jira and shadcn/ui. The repository describes itself as: Headless, composable ecommerce storefront built with Next.js, Typescript, and shadcn/ui. The licence is BSD-3-Clause.
When your agent uses it
- The user asks to retest
- Work through reported bugs/tickets one at a time
- Run the Phase 2 flow
- Pick the next ticket off the To Do column
Example prompts
- “run the Phase 2 flow”
- “/bug-retest-triage”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Evidence only. A verdict requires an artifact (screenshot, measurement, response capture) under qa/triage/evidence//. "Couldn't make it…
- Never fabricate. Missing repro steps, data, or credentials = STOP and ASK, never guess.
- One ticket at a time, on a shared board. Claim a ticket (move to "In testing") only after the prereq check passes — re-fetch first to…
- Don't force a verdict. Ambiguous/blocked → leave In testing, ASK, flag for review.
What it can do on your machine
Read from SKILL.md and the folder at commit c2ad30b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Bug Retest Triage loads about 888 tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 377 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mirumee/nimara-ecommerce at commit c2ad30b, republished under its BSD-3-Clause licence (© mirumee). 377 words, ~888 tokens.
Download SKILL.mdSave it as
.claude/skills/bug-retest-triage/SKILL.md (or your agent's skills folder).- name
- bug-retest-triage
- description
- Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask. Use this skill whenever the user asks to retest, re-verify, triage, or work through reported bugs/tickets one at a time; to "run the Phase 2 flow"; to pick the next ticket off the To Do column; or to confirm whether a fix holds. Works one ticket at a time on a board shared with human QA. Do NOT use for designing new test cases from a spec (use test-case-design) or for a broad regression pass (use regression-sweep).
Bug Retest & Triage
Retest reported defects on the live board and reach a defensible verdict, one ticket at a time, without ever fabricating data or forcing a result. This mirrors the project's CLAUDE.md "Phase 2" flow and the wiki note [[Bug Retest & Triage Process]].
Operating principles
- Evidence only. A verdict requires an artifact (screenshot, measurement, response capture) under
qa/triage/evidence/<KEY>/. "Couldn't make it fail" is not "fixed" — see [[Verdict & Evidence Policy]]. - Never fabricate. Missing repro steps, data, or credentials = STOP and ASK, never guess.
- One ticket at a time, on a shared board. Claim a ticket (move to "In testing") only after the prereq check passes — re-fetch first to confirm it's still To Do + unassigned; if taken, abandon and pick another.
- Don't force a verdict. Ambiguous/blocked → leave In testing, ASK, flag for review.
Before you start
Read [[Environments & Access Matrix]] and [[Jira & Board 74 Operating Manual]] (column↔status map, transition IDs, required customfield_10044, comment rules). Set READ_ONLY_MODE=false for board writes.
Workflow (per ticket)
- UNDERSTAND —
jira_get_issue(full: description, repro, expected vs actual, environment, comments, attachments). State in your own words what the defect is and what "still reproduces" vs "fixed" concretely looks like. Gaps in repro/expected = ASK trigger. - PLAN — write
qa/triage/plans/<KEY>.md: preconditions (env URL, account, data, cart state), steps, and explicit decision criteria (which observation → Open, which → Done). - CHECK PREREQS — ASK IF BLOCKED. Confirm env URL, credentials, specific data before opening the browser. If anything is missing/inaccessible/ambiguous: STOP and ASK, listing exactly what you need. Batch asks across tickets.
- CLAIM — re-fetch; if still To Do + unassigned,
jira_get_transitions→ transition to "In testing" (ID 25). - EXECUTE — drive the app via Playwright per the plan; pick the cheapest reliable method ([[Test Method Playbooks]]); run a control for ambiguous/flaky results. Screenshot the decisive step(s) →
qa/triage/evidence/<KEY>/. - CONCLUDE — on evidence only. No longer occurs → "Done" (31). Still occurs → "Open" (23). Backend-only → route to dev (label
dev_verify, → Open). Inconclusive/blocked → leave In testing, ASK. Add a factual comment viajira_add_comment(no AI/automation references): "Retested on <env/channel>: no longer reproduces —<one line>." / "...still reproduces —<one line>." - LOG — append
qa/triage/jira-actions.jsonand setretest_statusinqa/triage/worklist.json. Report, then next ticket.
Show full SKILL.md (20 more words)Show less
References
[[Bug Retest & Triage Process]] · [[Jira & Board 74 Operating Manual]] · [[Known Flaky, Blocked & Backend-Only]] · [[Test Method Playbooks]] · [[Verdict & Evidence Policy]]
© mirumee, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/bug-retest-triage of mirumee/nimara-ecommerce.
Open the folder on GitHubat commit c2ad30b
Compare with similar skills
Bug Retest Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bug Retest Triage this skillmirumee/nimara-ecommerce | 129 | — | ~888 | Automated safety check: Pass | BSD-3-Clause | |
| Generate Test Planopenshift-eng/ai-helpers | 120 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Test Case Managementpetrkindlmann/qa-skills | 170 | — | ~5k | Automated safety check: Pass | MIT | |
| Quality Engineering Quality AssuranceHoangNguyen0403/agent-skills-standard | 572 | — | ~629 | Automated safety check: Pass | MIT | |
| Quality Engineering Zephyr Coverage AnalysisHoangNguyen0403/agent-skills-standard | 572 | — | ~589 | Automated safety check: Pass | MIT | |
| Quality Engineering Zephyr Test GenerationHoangNguyen0403/agent-skills-standard | 572 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Test Case Management
petrkindlmann/qa-skills
Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase.
Quality Engineering Quality Assurance
HoangNguyen0403/agent-skills-standard
Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification.
Quality Engineering Zephyr Coverage Analysis
HoangNguyen0403/agent-skills-standard
Audit test coverage health, gaps, and QE debt for Jira stories or epics.
Quality Engineering Zephyr Test Generation
HoangNguyen0403/agent-skills-standard
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs.
- Official
Recommending Test Layers
bitwarden/ai-plugins
A skill your agent uses when deciding WHICH new tests a change needs and at WHICH layer each belongs, working from a Jira key, a Testmo CSV, an assessing-test-coverage report, a PR, or a feature…
More from mirumee/nimara-ecommerce
All 12 skills in this repoProject Guidelines
mirumee/nimara-ecommerce
Guide for working with Nimara's layered monorepo architecture.
Prd Modeling
mirumee/nimara-ecommerce
A skill your agent uses when creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.
Rfc Modeling
mirumee/nimara-ecommerce
A skill your agent uses when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
Ucp Agent
mirumee/nimara-ecommerce
Operate Nimara's UCP REST commerce API. An agent skill from mirumee/nimara-ecommerce.
Show Me
mirumee/nimara-ecommerce
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
Explore
mirumee/nimara-ecommerce
Ways to explore llm-wiki and answer from it. An agent skill from mirumee/nimara-ecommerce.
Related
Categories
Questions about Bug Retest Triage
What does Bug Retest Triage do?
Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask. Bug Retest Triage is an agent skill from mirumee/nimara-ecommerce. Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask.
When should I use Bug Retest Triage?
Bug Retest Triage fits situations like: the user asks to retest; work through reported bugs/tickets one at a time; run the Phase 2 flow; pick the next ticket off the To Do column.
How do I install Bug Retest Triage in Claude Code?
Run `npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a claude-code`. Or copy the skill folder (.claude/skills/bug-retest-triage in mirumee/nimara-ecommerce) into .claude/skills/bug-retest-triage in your project. Claude Code loads it when a task matches its description.
How do I install Bug Retest Triage in Codex?
Run `npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a codex`. Or copy the skill folder (.claude/skills/bug-retest-triage in mirumee/nimara-ecommerce) into .agents/skills/bug-retest-triage in your project. Codex loads it when a task matches its description.
Can I use Bug Retest Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mirumee/nimara-ecommerce --skill bug-retest-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-retest-triage, .gemini/skills/bug-retest-triage, .github/skills/bug-retest-triage and .opencode/skills/bug-retest-triage in your project.
What does Bug Retest Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Bug Retest Triage is instructions for the agent only.
Does Bug Retest Triage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Bug Retest Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Bug Retest Triage use?
Bug Retest Triage is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bug Retest Triage use?
About 888 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Bug Retest Triage?
Skills that share tags, products or a category with Bug Retest Triage: Generate Test Plan (openshift-eng/ai-helpers, 120 stars), Test Case Management (petrkindlmann/qa-skills, 170 stars), Quality Engineering Quality Assurance (HoangNguyen0403/agent-skills-standard, 572 stars) and Quality Engineering Zephyr Coverage Analysis (HoangNguyen0403/agent-skills-standard, 572 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bug Retest Triage?
mirumee (a GitHub organization) maintains it in mirumee/nimara-ecommerce, which has 129 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: mirumee/nimara-ecommerce on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.