Loading...
Loading...
Found 182 Skills
Execute work plans efficiently while maintaining quality and finishing features
Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.
This skill should be used when the user asks to "implement a plan", "execute implementation", "build from plan", "implement feature", or needs to orchestrate execution of an implementation plan with specialized engineering agents.
Use this skill when the user asks to review their local git changes, staged or unstaged diffs, or wants a code review before committing. Triggers on "review my changes", "review staged", "review my diff", "check my code", "code review local changes", "review unstaged", "review before commit".
Multi-layer quality assurance with 5-layer verification pyramid (Rules → Functional → Visual → Integration → Quality Scoring). Independent verification with LLM-as-judge and Agent-as-a-Judge patterns. Score 0-100 with ≥90 threshold. Use when verifying code quality, security scanning, preventing test gaming, comprehensive QA, or ensuring production readiness through multi-layer validation.
Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation
Review a GitLab Merge Request and provide findings, and post structured review comments with issue explanation plus pseudo code fixes. Use this skill when asked to review a Gitlab Merge request.
Use Codex CLI for sandboxed auditing, debugging, and autonomous prototyping
Run Python quality checks with ruff, pytest, mypy, and bandit in deterministic order. Use WHEN user requests "quality gate", "lint", "verify code quality", "check python", or "pre-commit check". Use for pre-merge validation, CI/CD gating, or comprehensive code quality reports. Do NOT use for single-tool runs (run tool directly), debugging runtime bugs (use systematic-debugging), refactoring (use systematic-refactoring), or architecture review.
Verify cross-component wiring: exports are imported AND used, real data flows through connections, output shapes match input expectations. Use after /feature-implement, before /feature-validate, or standalone on any codebase. Use for "check integration", "verify wiring", "are components connected", "integration check", or "/integration-checker". Do NOT use for unit test failures, linting, or single-file correctness issues.
Use when validating subjective quality criteria that cannot be deterministically tested — applies LLM-based evaluation with structured rubrics for tone, aesthetics, UX feel, documentation quality, and code readability. Triggers: documentation quality check, error message tone review, UX copy evaluation, code readability assessment, design aesthetic review.
QA validation and fix loop workflow — validates implementation completeness then iterates fix cycles until all acceptance criteria pass and quality gates clear