Code review methodology and quality standards for comprehensive code analysis. Use to understand WHAT and HOW to review code: 11 review dimensions, process, quality standards.
Sets up dev infrastructure for new projects: framework init, folder structure, Docker, pre-commit hooks (gitleaks), testing infrastructure, .gitignore.
Run 2-3 features in parallel across independent sessions without breaking the live platform: isolate each feature (branch + git worktree), coordinate through shared repo files (never session memory), and converge via a serialized integration train (rebase -> migration merge -> PR/CI -> ephemeral staging smoke -> merge -> per-service deploy). One session = one feature = one track.
Stops current work on user request, captures full session state to project docs, and generates a resume prompt so the next session can continue without loss.
Pre-deploy acceptance testing methodology: run test suite (unit/integration/E2E), verify acceptance criteria from user-spec and tech-spec. Does not require live environment.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.