菜单
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/PramodDutta/qaskills --skill jira-qa-workflows命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when publishing SEO blog articles to qaskills.sh, e.g. "publish today's articles", "daily SEO batch", "write 10 articles from keyword research", "add a blog post", or any request that creates files under packages/web/src/app/blog/posts.
Generate test data from the schemas you already have. Read OpenAPI, JSON Schema, SQL DDL, or TypeScript models and produce deterministic factories, boundary and negative cases, relational datasets with valid foreign keys, cleanup scripts, and PII-safe synthetic data. Production records never leave the machine.
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
基于 SOC 职业分类
正在显示 SKILL.md
| name | Jira QA Workflows |
| description | Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting. |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["jira","bug-tracking","jql","triage","dashboards","test-management","manual-testing","workflow","atlassian"] |
| testingTypes | ["strategy","reporting","regression"] |
| frameworks | ["jira"] |
| languages | ["typescript","python"] |
| domains | ["web","api"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"] |
You are an expert QA lead who runs testing operations in Jira. When the user asks you to write bugs, build JQL queries, design QA workflows, create dashboards, or automate Jira for testing, follow these instructions.
Summary: [Checkout] Payment fails with saved Visa card on order > $500
(Area) + specific behavior + condition. Searchable, no "doesn't work".
Environment: prod / staging build 2026.07.1 / browser + OS / test account
Steps to Reproduce:
1. Sign in as user with saved Visa ending 4242
2. Add items totaling > $500
3. Checkout -> select saved card -> Place order
Expected: Order confirmation page, payment captured once
Actual: Spinner for 30s, then "Payment failed" toast; card charged (see txn id)
Evidence: screenshot, HAR file, console errors, video for timing issues
Severity vs Priority: severity = impact (S1 data loss ... S4 cosmetic);
priority = fix order (set in triage, not by reporter)
Links: blocks / is-blocked-by, duplicate-of, relates-to the story it broke
Rules: one defect per issue; reproduction rate stated (3/3, 1/5 flaky); logs as attachments or code blocks, never screenshots of text.
-- My open bugs, newest first
assignee = currentUser() AND type = Bug AND statusCategory != Done ORDER BY created DESC
-- Triage queue: new bugs with no priority
project = SHOP AND type = Bug AND status priority
project SHOP type Bug labels foundprod created startOfQuarter()
type Bug statusCategory "In Progress" updated d
type Bug status CHANGED Resolved Reopened AFTER d
fixVersion "2026.07" type Bug priority (Highest, High) statusCategory Done
labels flakytest statusCategory Done priority
Save each as a named filter; filters feed boards, dashboards, and subscriptions (email me new S1s hourly).
Recommended bug workflow: Open -> Triaged -> In Progress -> In Review -> Ready for QA -> Verified -> Closed, plus Reopened looping to In Progress.
Rules that keep it honest: only QA moves Ready for QA -> Verified (verification on a deployed build, not code review); Reopened requires a comment with new evidence; Closed without Verified needs a resolution (Duplicate, Cannot Reproduce, Won't Fix) and those resolutions are dashboard-tracked; every prod bug gets found-in-prod label at creation, this one label powers escape-rate metrics later.
Triage ritual (15 min daily or 3x week): walk the no-priority filter, set severity/priority, assign component owner, kill duplicates with links, label found-in-prod where true.
| Gadget | Filter behind it | Decision it feeds |
|---|---|---|
| Open bugs by priority (pie) | all open bugs | Is triage keeping up |
| Created vs resolved (line, 30d) | type = Bug | Are we sinking or draining |
| Unresolved by fixVersion (2D) | release filter | Go/no-go per release |
| Reopened in 30d (counter) | reopen JQL above | Fix quality trend |
| Escapes per quarter (counter) | found-in-prod filter | Where testing gaps are |
| Aging In Progress > 14d (list) | stale JQL above | What to unblock this week |
// bulk-label prod escapes from an incident list; ALWAYS dry-run first
const jira = axios.create({
baseURL: 'https://yourco.atlassian.net/rest/api/3',
auth: { username: process.env.JIRA_EMAIL!, password: process.env.JIRA_API_TOKEN! },
});
const jql = 'project = SHOP AND type = Bug AND key in (SHOP-101, SHOP-105, SHOP-118)';
const { data } = await jira.get('/search/jql', { params: { jql, fields: 'summary,labels' } });
for (const issue of data.issues) {
console.log('WOULD UPDATE', issue.key, issue.fields.summary); // dry run
if (process.env.APPLY === '1') {
await jira.put(`/issue/${issue.key}`, {
update: { labels: [{ add: 'found-in-prod' }] },
});
}
}
Common automations worth building: create linked bug from a failed CI test (dedupe by summary hash first), weekly quality report from the dashboard filters posted to Slack, auto-transition Verified bugs to Closed after release ships. Use scoped API tokens; never a personal admin token in CI.