Skip to content

fix: improve copy-simple-qa-cases skill with PR number support #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
b4tchkn merged 1 commit into from
Feb 18, 2026
Merged

fix: improve copy-simple-qa-cases skill with PR number support #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion plugins/qa-toolbox/copy-simple-qa-cases/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,22 @@ Generate concise, well-structured test cases from the current branch's code chan

### 1. Gather Context

Collect all necessary information:
Parse `$ARGUMENTS` to extract:

- **PR number**: If a numeric value is found in `$ARGUMENTS`, use it as the target PR number
- **Language flag**: Check for `--lang ja` or `--lang en`

#### If PR number is specified:

Use `gh pr` commands with the PR number to fetch context from that specific PR:

- **PR body**: !`gh pr view $PR_NUMBER --json body --jq '.body'`
- **PR diff**: !`gh pr diff $PR_NUMBER`
- **Commit messages**: !`gh pr view $PR_NUMBER --json commits --jq '.commits[].messageHeadline'`

#### If no PR number is specified:

Use the current branch's context:

- **PR body**: !`gh pr view --json body --jq '.body' 2>/dev/null || echo "No PR found"`
- **Branch diff summary**: !`git diff develop --stat 2>/dev/null || git diff main --stat 2>/dev/null || echo "No diff found"`
Expand All @@ -35,6 +50,7 @@ From the gathered context, identify:
Write test cases in **Markdown format** with the following rules:

#### Language

- Default: English
- If `$ARGUMENTS` contains `--lang ja` or Japanese text, write in Japanese

Expand All @@ -44,16 +60,19 @@ Write test cases in **Markdown format** with the following rules:
## Test Cases: {Brief title describing the change}

### Background

{1-2 sentences: what was changed/fixed and why}

---

### TC1: {Test case name}

- **Precondition**: {Required state before testing}
- **Steps**: {What to do}
- **Expected**: {What should happen}

### TC2: {Test case name}

- **Precondition**: {Required state before testing}
- **Steps**: {What to do}
- **Expected**: {What should happen}
Expand All @@ -62,6 +81,7 @@ Write test cases in **Markdown format** with the following rules:
```

#### Guidelines

- Keep each field to **1-2 sentences max** - QA engineers should be able to scan quickly
- Focus on **user-visible behavior**, not implementation details
- Include the **most critical/risky scenario** as a separate test case
Expand Down