Test Strategy Gap Review
Use when the main question is whether current verification is sufficient for a change, which test layers are missing, and where the smallest high-value regression protection should be added.
Docs Writer
Use when completed or in-progress work needs documentation such as README updates, migration notes, release notes, usage examples, or developer-facing operational guidance. This skill writes docs grounded in the current code and verified behavior.
Systematic Debugging
Use when a bug, flaky test, or runtime failure does not have an obvious root cause. This skill emphasizes reproduction, narrowing the search space, hypothesis testing, and evidence before proposing a fix.
Incident Observability Triage
Use when a problem is driven by alerts, logs, metrics, traces, dashboards, or visible production impact. This skill focuses on blast radius, mitigation direction, and telemetry-first investigation before jumping into implementation.
Dependency Compliance Audit
Use when the main question is whether a third-party dependency is acceptable to adopt, upgrade, keep, or ship. This skill focuses on package risk, license or policy fit, supply-chain awareness, and recommended next actions.
Api Contract Compatibility Review
Use when an API, schema, payload, event, or contract change must be checked for backward compatibility, client impact, versioning risk, and migration safety.
Security Review
Use when a change affects trust boundaries such as authentication, authorization, untrusted input, secrets, or sensitive data handling. This skill identifies security risks, abuse cases, and verification steps without replacing implementation review.
Planning
Use when a task needs scope clarification, acceptance criteria, implementation slicing, dependency mapping, or a verification plan before coding begins. This skill turns fuzzy requests into concrete execution plans.
Release Rollout Strategy
Use when a change is shippable in principle but still needs a safer rollout shape, rollback plan, monitoring checkpoints, or staged release execution strategy.
Cost Impact Review
Use when a change may increase infrastructure or runtime cost (compute, storage, network egress, third-party API calls, observability volume) and the team needs a focused cost-impact review before merge or rollout.
Change Impact Analysis
Use when the main question is what a proposed or partial change will affect across code, interfaces, configs, tests, docs, consumers, and rollout surfaces. This skill maps blast radius before implementation, merge, or release.
Performance Investigation
Use when the main problem is latency, throughput, memory, resource usage, render slowness, or another performance bottleneck that needs investigation and prioritization.
Environment Config Audit
Use when the main risk is environment parity, config drift, secrets wiring, flags, defaults, or deployment-time assumptions rather than code logic itself.
Review Address Comments
Use when review comments, requested changes, or PR feedback must be processed systematically. This skill groups comments, decides what to accept, and turns feedback into verified edits instead of ad hoc reactions.
Dev Workflow Kit
Use when a software task needs lifecycle support around coding itself: planning, debugging, CI repair, review comment resolution, browser verification, security review, ship-readiness, documentation writing, and other workflow analysis around delivery.
Architecture Refactor Guidance
Use when the core problem is structural change: boundaries, coupling, module seams, interface extraction, or safe refactor sequencing. This skill helps decide how to reshape code without turning implementation into guesswork.
Release Incident Postmortem
Use when an incident has already been mitigated and the team needs a structured post-incident retrospective with timeline, impact, root cause, contributing factors, and follow-up actions.
Fix Ci
Use when CI, build, lint, type-check, or test automation is failing and the branch is blocked. This skill focuses on reading the earliest failure, classifying the failure surface, and choosing the smallest repair that restores pipeline health.
Browser Verification
Use when a change needs browser-level evidence such as UI flow checks, form interaction validation, console inspection, or end-to-end smoke verification. This skill focuses on observable behavior instead of code assumptions.
Data Quality Audit
Use when existing data correctness, freshness, completeness, or constraint integrity is in question at runtime, distinct from migration-time safety.
Ship Readiness
Use when work is nearly complete and needs a final readiness check for merge, release, or deployment. This skill focuses on remaining blockers, verification state, risks, rollback awareness, and documentation gaps.
Data Migration Safety Review
Use when a schema change, backfill, data migration, or persistence-layer transition must be reviewed for rollout order, reversibility, backfill safety, and operational risk.