Debugging
Investigate failures whose root cause is still unknown — narrow the search space, instrument, and test falsifiable hypotheses. Use for intermittent or environment-dependent behavior, unexplained stack traces, regressions with no known trigger, or any symptom without a confirmed cause. Ends once the root cause is identified; the fix and its regression test belong to bug-fix. For a flaky test over…
Terraform Review
Method for reviewing Terraform/OpenTofu infrastructure-as-code changes for blast radius, state safety, and drift before apply. Use when reviewing a Terraform plan or diff, writing or changing .tf files, restructuring modules, or before running terraform apply. Reviews the implementation of a design — designing the infrastructure itself belongs to infra-design; for IAM/secret depth also use securi…
Security Audit
Security review and hardening workflow — root-cause analysis of vulnerabilities, authentication and authorization checks, least privilege, input handling, secret hygiene, and security regression tests. Use when reviewing code for security, fixing a vulnerability, hardening a feature, or handling auth, permissions, secrets, or untrusted input. For a quick automated pass on pending changes, the bui…
Infra Design
Simplest-first workflow for designing and proposing infrastructure — pin the requirements, draft the minimal design, then add complexity only where performance, reliability, security, or cost demands justify it. Use when designing new infrastructure, proposing a deployment or hosting architecture, choosing between managed services, planning capacity and scaling, or comparing infrastructure option…
Bug Fix
Regression-first workflow for fixing a defect whose cause is known. Reproduce the confirmed defect, fix the root cause minimally, protect it with a regression test, and verify. If the root cause is still unknown, use the debugging skill first.
Testing
Strategy and rules for writing or improving automated tests. Use when adding tests, improving coverage, fixing flaky tests, setting up a test suite, or deciding what and how to test. Emphasizes deterministic tests, testing behavior over implementation, and a tight validation loop. For diagnosing production failures whose cause is unknown, use the debugging skill. Once the cause is identified, bug…
Code Quality Review
Checklist and method for reviewing code quality — readability, maintainability, SOLID, DRY, performance, and backward compatibility. Use when asked to review code, a diff, a branch, or a merge request for quality, or before finalizing significant changes. For GitHub PR review use the built-in /review; for security-focused review use the security-audit skill.
Architecture Review
Method for assessing a codebase's structure — duplication, single-responsibility violations, layering problems, and coupling — and recommending minimal, incremental improvements. Use when asked to review architecture, assess structure or technical debt, evaluate module boundaries, or plan a refactor. Reviews the system, not a single change: for reviewing one diff or branch use the code-quality-re…