Cs Issue Report
liuzhengdongfortest/codestableTurning a problem into a clear written record is the first step to fixing it. This skill helps you describe what you saw, not guess why it happened. It asks five simple questions one at a time to capture everything needed.
You answer what you saw, how to repeat it, what you expected, your setup, and how serious it is. The skill checks for fuzzy answers and pushes for clear details. It never mixes in guesses about the root cause.
After the report is done, the skill picks a path. If the cause is clear from reading the code, it takes the fast track to fix it right away. If not, it goes to the standard path for a deeper analysis later.
Add Cs Issue Report skill to your workflow
Global
mkdir -p ~/.claude/skills/cs-issue-reportProject
mkdir -p .claude/skills/cs-issue-reportSource Repository
More Testing & QA Claude Code Skills
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step