staging-qa-doc
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Generate or update a Claude Doc of manual QA test scenarios covering everything that is on the `staging` branch but not yet on `main` (origin/main...origin/staging). Reads the commits, the code diffs and the tests they add to write precise, step-by-step "Cas N — Titre" scenarios (exact UI labels, routes, expected results in bold, ready-to-paste CSV/data blocks), a prerequisites section and smoke tests per role for technical changes, built for the tester — one-click status dropdown per case (À tester / OK / KO / Bloqué / À retester / Obsolète) in a boxed case header, steps as a table (# / Action / Attendu / Résultat checkbox / Capture) and a linked summary table. On rerun within the same cycle (main base unchanged) it updates the existing doc in place — adds cases for new commits, flags "À retester" cases touched by later fixes, strikes obsolete ones, never touches the user's screenshots or comments; after staging is merged into main it starts a new doc. Use when the user wants a QA / test-scenario document for staging vs main, or invokes /staging-qa-doc. Not the same as the `qc` skill (which tests one issues/ feature against SPEC.md).
- Reads credentials
In this repository9 other files it gives its agents.
- doc-to-issuesSkill
- documentationSkill
- implement-backlogSkill
- implement-issueSkill
- interviewSkill
- polishSkill
- qcSkill
- reportSkill
- review-issueSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 12 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.