Install any skill in seconds. Free to start, no credit card required.
Get Started Free →quran/test-plan
Generates a comprehensive testing plan based on the current branch changes or a specific PR.
Passed 10 of 19 test cases with the skill, and 10 of 19 without it.
and 1 more in the full report
3 fixed13 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm ready to review local changes on my branch before creating a PR. The project repository's main deployment branch is named `production`. I plan to use `git diff main...HEAD` to inspect changes. Is that command correct?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies `git diff production...HEAD` as the diff command. | Missed | Passed |
| Rejects using `main` as the default target branch in favor of `production`. | Passed | Passed |
The instructions your model reads when the skill loads.
Generate a comprehensive testing plan based on the current branch changes or a specific PR.
$ARGUMENTS can be:
production2732 - fetches that PR's diffGet the diff:
$ARGUMENTS is empty: git diff production...HEAD$ARGUMENTS is a PR number: gh pr diff {PR_NUMBER}Read docs/COMMON_MISTAKES.md for patterns that have caused production bugs
Analyze the changes:
Generate the testing plan using the criteria below and output format
dangerouslySetInnerHTMLtest cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.