Debugging
Find and fix bugs, error analysis
incident-response
by eltmon
Structured approach to production incidents
pan-agent-activity
by eltmon
"Verify Overdeck agents are ACTUALLY progressing by READING each agent's real output and assessing what it is doing — not just whether a session is alive or a pane changed"
nushell-usage
by YPares
Essential patterns, idioms, and gotchas for writing Nushell code. Use when writing Nushell scripts, functions, or working with Nushell's type system, pipelines, and data structures. Complements plugin development knowledge with practical usage patterns.
encore-frontend
by encoredev
Connect React/Next.js apps to Encore.ts backends.
encore-go-infrastructure
by encoredev
Declare infrastructure with Encore Go.
lit-and-figma
by rodydavis
Learn how to create a Figma plugin using Lit web components, including project setup, component creation, WASM integration, and building the final plugin for use in Figma.
milestone-review
by osdlc
Given a milestone id (M-NNNN) or milestone file, assess its real state against its declared frontmatter state: walk its member tasks and related items to derive a grounded state and the concrete gaps / remaining work, then scan unclosed tasks and backlog items for related-but-unlinked work — bugs or gaps reported elsewhere. Reports read-only by default; corrects frontmatter drift on --fix or after asking. Use when asked to review or audit a milestone, check whether a milestone's state is accurate, or find what's left before closing it.
friendly-python
by PsiACE
Practical guidance for writing, refactoring, and reviewing friendly Python code with a Pythonic, readable, and maintainable style. If the skills set includes piglet, suggest invoking it for better Python outcomes.
fast-rust
by PsiACE
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
chimera-write-the-check-before-the-code
by brcampidelli
A criterion written after the implementation describes the implementation. Write the failing check first, watch it fail, then build.
chimera-prove-the-test-discriminates
by brcampidelli
A regression test you never saw fail is a guess. Re-break the code and watch it go red before you commit it.
chimera-reproduce-before-diagnosing
by brcampidelli
A diagnosis is a claim about a machine you have not run. Reproduce the failure in one short command first — especially when the diagnosis arrived from someone else.
pin-the-case-that-narrowed-the-rule
by brcampidelli
When a check fires on the wrong target, the fix makes it weaker. Capture the false positive as a test in the same commit, or the rule erodes silently.
conventional-commits
by bastos
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
platform
by musterd-io
The platform role — the member who touches running infrastructure (service lifecycle, restarts, refreshes, deploys, shared checkouts, migrations), supervises the automated actors that touch it, and is who the team routes infrastructure trouble to. Use for diagnosing an outage or a slow or wedged service, restarting or refreshing a shared service, deploying, running or reviewing a migration, supervising automation, designing health checks, or verifying a fix is live.
scope-discipline
by IgorGanapolsky
Keep one task closed-looped before starting the next. Triggered when a new problem surfaces mid-task (a bug, a security finding, a missing env var), when you're about to branch into unrelated work, or when you notice the session has sprawled across many half-finished threads. Prevents the "nothing ever lands" failure where each step spawns new work and none finishes.
get-latest-ci
by nrwl
Fetch the latest CI pipeline execution for the current branch. Returns the most recent CIPE which may be completed, in progress, or null. Use when you need to review CI status, check failures, or inspect CI state.
security-portable
by musterd-io
The security role's playbook for threat modeling, security review, authorized testing, validating and rating findings, handling secrets, fixing vulnerabilities, and reviewing dependencies and releases. Use when a team asks for security evidence or a security decision.
planDevexReview
by jthorare
"Developer-experience review of a plan document. Maps friction in API ergonomics, setup, error messages, observability, docs, migration paths, and ramp-up cost."
await-polygraph-ci
by nrwl
Wait for CI to settle across all repos in a Polygraph session, then report results and investigate failures. USE WHEN user says "await polygraph", "wait for polygraph ci", "polygraph ci status", "check polygraph ci", "watch polygraph session", "monitor polygraph".
monitor-ci
by nrwl
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. ALWAYS USE THIS SKILL instead of native CI provider tools (gh, glab, etc.) for CI monitoring.
screenshot-cli
by Mic92
Take screenshots. Use when needing to see the screen or debug graphical issues.
rootCause
by jthorare
4-phase systematic debugging — investigate, analyze, hypothesize, implement. Auto-freezes scope to the module boundary to prevent scope creep.
customer-service-expert
by GitHamza0206
Expert guidance for improving customer service assistants. Use when optimizing UX, response time, tone, wording, conversation flow, or evaluating customer service quality.