200 skills · sorted by relevance
Guides debugging through reproduction, comparison with working examples, hypothesis testing, and a focused fix. It starts with a repeatable check for the exact symptom and uses regression tests to verify the result.
Develop and fix code by first writing a failing test, then making it pass and improving the implementation. The skill follows the project's testing tools and checks both the intended behavior and existing functionality.
Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.
Build features or fix bugs by writing a small test first, checking that it fails for the expected reason, and making the smallest code change needed. Run related tests and review the changes for unintended effects.
Guide Rust development through test-driven development: write a failing test, implement enough code to pass, then refactor. Includes practical test patterns and final checks for formatting, static analysis, and test results.
Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.
Create automated shell script tests with Bats, a Bash testing tool. Check exit codes, output, and failure cases, organize reusable test helpers and data, and run checks across shells or in CI/CD pipelines.
Create and organize Python tests with pytest. Use reusable setup, mock replacements for external services, controlled test time, and coverage reports to check normal behavior, failures, retries, and interactions between application components.
Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.
Design workflows that evaluate and refine AI outputs through self-review, separate generation and evaluation roles, tests, or weighted scoring criteria. Includes patterns for structured feedback, iteration limits, and stopping when quality stops improving.
Guide development from problem definition and planning through testing, debugging, review, and final verification. It uses test-driven development, writing a failing test before implementation, and requires evidence before reporting work as complete.
Carry out an existing implementation plan one task at a time in the current session. Verify each task with tests, record progress and decisions in a file, and review the whole branch after implementation.
Investigate bugs, failing tests, and unexpected behavior through reproducible steps, logs, and comparisons with working code. Follow four stages to identify the root cause, test a hypothesis, apply a focused fix, and verify the result.
Develop features and fix bugs by writing a behavior test first, observing its expected failure, and adding the minimum code needed to pass. Then clean up the code while keeping tests passing, applying this process where regression risk warrants it.
Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
The English summary is being prepared. Showing the original description.
Collaboratively build and refine paper screening rubrics through brainstorming, test-driven development, and iterative feedback
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code
The English summary is being prepared. Showing the original description.
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code
The English summary is being prepared. Showing the original description.
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
The English summary is being prepared. Showing the original description.
Unified TDD skill with three input modes — from spec, from task, or from description. Enforces test-first development using repository patterns, with proptest guidance and backpressure integration.
The English summary is being prepared. Showing the original description.
Test-driven development workflow with Red-Green-Refactor cycle across languages
The English summary is being prepared. Showing the original description.
Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.
The English summary is being prepared. Showing the original description.