Testing
Unit tests, integration tests, test automation
executing-plans
by axiomantic
"Use when you have a written implementation plan to execute"
resolving-merge-conflicts
by axiomantic
"Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (<<<<<<< =======), or need help resolving conflicted files"
assembling-context
by axiomantic
"Prepare tiered context packages for subagents and manage token budgets. Triggered by 'prepare context for', 'assemble context', 'token budget', or invoked by implementing-features Phase 3.5/4.2."
debugging
by axiomantic
"Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack trace/error output. NOT for: test quality issues (use fixing-tests), adding new behavior (use implementing-features)."
reviewing-impl-plans
by axiomantic
"Use when reviewing implementation plans before execution, especially plans derived from design documents"
android-emulator-skill
by fluxxion82
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and emulator lifecycle management. Optimized for AI agents with minimal token output. Android equivalent of ios-simulator-skill.
fixing-tests
by axiomantic
"Use when tests themselves are broken, test quality is poor, or user wants to fix/improve tests. Triggers: 'test is broken', 'test is wrong', 'test is flaky', 'make tests pass', 'tests need updating', 'green mirage', 'tests pass but shouldn't', 'audit report findings', 'run and fix tests'. Three modes: fix specific tests, process green-mirage audit findings, and run-then-fix. NOT for: bugs in production code caught by correct tests (use debugging)."
merging-worktrees
by axiomantic
"Use when merging parallel worktrees back together after parallel implementation, combining parallel development tracks, or unifying branches from dispatched parallel agents. Triggers: 'merge worktrees', 'combine parallel branches', 'integrate parallel work', 'all tracks complete', 'bring everything together'."
test-driven-development
by axiomantic
"Use when user explicitly requests test-driven development, says 'TDD', 'write tests first', 'red green refactor', 'test-first', or 'start with the test'. Also invoked as a sub-skill by implementing-features and executing-plans for each implementation task. NOT a replacement for implementing-features for full feature work."
enforcing-code-quality
by axiomantic
Use when writing or modifying code. Enforces production-quality standards, prohibits common shortcuts, and ensures pre-existing issues are addressed. Invoked automatically by implementing-features and test-driven-development.
auditing-green-mirage
by axiomantic
"Use when auditing whether tests genuinely catch failures, or when user expresses doubt about test quality. Triggers: 'are these tests real', 'do tests catch bugs', 'tests pass but I don't trust them', 'test quality audit', 'green mirage', 'shallow tests', 'tests always pass suspiciously', 'would this test fail if code was broken'. Forensic analysis of assertions, mock usage, and code path coverage."
isolated-testing
by axiomantic
Use when testing theories during debugging, or when chaos is detected. Triggers: "let me try", "maybe if I", "what about", "quick test", "see if", rapid context switching, multiple changes without isolation. Enforces one-theory-one-test discipline. Invoked automatically by debugging, scientific-debugging, systematic-debugging before any experiment execution.
performance-optimization
by ThibautBaissac
Identifies and fixes Rails performance issues including N+1 queries, slow queries, and memory problems. Use when optimizing queries, fixing N+1 issues, improving response times, or when user mentions performance, slow, optimization, or Bullet gem.
openspec-verify-change
by alibaba
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-bulk-archive-change
by alibaba
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-bulk-archive-change
by alibaba
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-sync-specs
by alibaba
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-sync-specs
by alibaba
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-verify-change
by alibaba
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
api-tester
by aibangjuxin
You are a detail-oriented and methodical API Tester. You are an expert at testing the functionality, reliability, performance, and security of APIs. You are proficient with tools like Postman, Insomnia, and automated testing frameworks like pytest or jest to write and execute API tests.
test-results-analyzer
by aibangjuxin
You are a data-driven and insightful Test Results Analyzer. You are an expert at looking at the output of large, automated test suites, identifying patterns, and triaging failures. You help the engineering team quickly understand the health of a new build and prioritize which test failures to fix first.
rapid-prototyper
by aibangjuxin
You are a creative and resourceful Rapid Prototyper, a jack-of-all-trades engineer who can quickly build functional prototypes to test new ideas. You are proficient in a wide range of technologies and know how to choose the right tool for the job to get a working demo up and running in record time. You are pragmatic and focus on speed and functionality over perfection.
growth-hacker
by aibangjuxin
You are a data-driven and creative Growth Hacker. You live at the intersection of marketing, product, and engineering. You are relentlessly focused on finding scalable and unconventional ways to grow a user base. You are an expert in experimentation, A/B testing, and analyzing data to find growth levers.
cf-fix
by dinhanhthi
Quick bug fix workflow. Use when the user reports a bug, error, or broken behavior — e.g. "fix this", "it's broken", "not working", "there's a bug", "I'm getting an error", "this crashes", "something is wrong", "why does this fail", "debug this", "it throws", "fix the issue", "resolve this error", "help me fix", "can you fix", "this doesn't work", "stopped working", "regression", "unexpected behavior", "failing test", "broken after update". Also triggers on stack traces, error messages, or descriptions of incorrect program behavior.