- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
github-copilot-cli
by WilsonLe
Efficient daily use of GitHub Copilot CLI for senior engineers. Use when planning, prompting, reviewing, or chaining Copilot CLI commands (gh copilot) to explore codebases, draft changes, debug issues, or accelerate workflows without losing architectural intent.
claude-agent-sentry-issue-summarizer
by monkey1sai
Converted from Claude plugin agent "issue-summarizer" (sentry). Use when
flowglad-feature-gating
by flowglad
Implement feature access checks using Flowglad to gate premium features, create paywalls, and restrict functionality based on subscription status. Use this skill when adding paid-only features or checking user entitlements.
Debugging
by wollfoo
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims. Sử dụng khi gặp lỗi, bug, test fail, không hoạt động, crash, exception, sửa lỗi, debug.
implement
by doodledood
"Execute implementation plans in-place with verification loops. Implements chunks sequentially, runs quality gates, auto-fixes failures. Use after $plan or with inline tasks. Triggers: implement, build, code, execute plan."
avoid-inferable-annotations
by marius-townhouse
Use when writing type annotations on variables. Use when TypeScript can infer the type. Use when code feels cluttered with types.
bugfix
by doodledood
"Systematic bug investigation and fix workflow. Gathers symptoms, forms hypotheses, investigates root cause, implements fix, and verifies. Use for debugging, fixing errors, or troubleshooting. Triggers: debug, fix bug, troubleshoot, why is this broken."
review
by jforksy
Comprehensive code review checking logging, error handling, TypeScript, and production readiness
code-quality
by AlexanderStephenThompson
Non-negotiable code quality standards for testing, structure, naming, error handling, and documentation
graphql-mutations
by jovermier
GraphQL mutation design including payload patterns, field-specific errors, input objects, and HTTP semantics. Use when designing or implementing GraphQL mutations.
roast-my-code
by sakimyto
"Comprehensive code review in roast style. Analyzes security, architecture, complexity, TDD compliance, type safety, error handling, naming, dead code, performance, dependencies, API design, frontend quality, and git hygiene. Delivers findings as entertaining roasts with actionable fixes. Use /roast to review your codebase. Supports --level (gentle/spicy/savage/sensei)."
spec-step-execution
by wilddeer
You MUST use this EVERY time you are executing a single step from a spec.
m3-web-ink
by shelbeely
Implement Material Design 3 in terminal CLIs using Ink (React for CLIs) with @inkjs/ui components. Covers M3 token mapping to terminal colors, ThemeProvider setup, component mapping, and ANSI fallbacks. Use this when building M3-styled command-line interfaces.
fix-review-issues
by doodledood
"Orchestrate fixing issues found by $review. Handles issue discovery, user confirmation, plan creation, and execution via $implement. Triggers: fix review issues, fix findings, address review feedback."
davenov:cc:expert-build-nostr
by kaladivo
Build Nostr applications for decentralized data exchange between clients. Full lifecycle - implement pub/sub messaging, relay connections, event handling, encryption, and custom protocols. Uses nostr-tools library.
flowglad-checkout
by flowglad
Implement checkout sessions for purchasing subscriptions and products with Flowglad. Use this skill when creating upgrade buttons, purchase flows, or redirecting users to hosted checkout pages.
Minimum Lovable Product (MLP)
by Coowoolf
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
rp-cli-investigate
by carmandale
"Deep investigation workflow using rp-cli and RepoPrompt's context builder. Use when investigating bugs, understanding codebases, or tracing issues through complex systems. CRITICAL: Do not timeout rp-cli commands."
workflow-builder
by mindmorass
Design and implement multi-step automation workflows
spec-flow-analyzer
by carmandale
Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation.
information-software-design
by madeyexz
Design principles from Bret Victor's "Magic Ink" for building information software. Use when designing dashboards, search results, calendars, finance apps, or any interface where users seek answers rather than manipulate objects. Ask "what can the user learn?" not "what can the user do?"
go-concurrency
by jovermier
Go concurrency patterns including goroutines, channels, context propagation, and sync primitives. Use when working with goroutines, channels, context.Context, or any concurrent Go code.
reviewing-code
by oryanmoshe
Reviews code changes for bugs, performance issues, security problems, and best practice violations. Use when reviewing PRs, before committing, after making code changes, or when user asks to review, check, or look over code. Catches N+1 queries, missing error handling, React hooks issues, test coverage gaps, and security vulnerabilities.
committing-code
by oryanmoshe
Writes git commit messages using conventional commits format with gitmoji. Use when creating git commits, preparing commit messages, or when the user asks to commit changes. Triggers on "commit", "git commit", "save changes", or any request to record changes to version control.