- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
solo-stream
by fortunto2
Interactive decision-making wizard using STREAM 6-layer framework for founders facing high-stakes choices. Use when user says "help me decide", "should I do this", "evaluate decision", "STREAM analysis", "run decision framework", or "pros and cons". Do NOT use for idea validation with PRD (use /validate).
address-pr-comments
by doodledood
'Triage and fix PR review comments. Reads comments, filters false positives (outdated, misread, wrong context, style preference), validates relevance against current diff, and fixes valid ones with confirmation. Use when: "fix pr comments", "address review feedback", "handle pr feedback".'
review
by doodledood
Production-level PR review using consultant agent. 10-category framework focused on correctness.
solo-review
by fortunto2
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).
algorand-typescript
by algorand-devrel
Syntax rules and patterns for Algorand TypeScript (PuyaTs) smart contracts. Use when writing TypeScript contract code, encountering Puya compiler errors, asking about AVM types or value semantics, needing guidance on storage patterns (GlobalState, BoxMap), or asking about clone(), arrays, or inner transactions. Strong triggers include "Puya compiler error", "How do I use uint64?", "What is clone() for?", "BoxMap not working", "AVM type error", "GlobalState not updating".
troubleshoot-errors
by algorand-devrel
Diagnose and fix common Algorand errors including smart contract failures, transaction rejections, and SDK exceptions. Use when encountering smart contract logic errors or assertion failures, transaction rejections or confirmation timeouts, SDK exceptions (AlgodHTTPError, LogicError), account-related errors (insufficient balance, not opted in), or ABI encoding/decoding errors. Strong triggers include "logic eval error", "assert failed", "overspend", "transaction rejected", "pc=X" in error messages, "opcode budget exceeded", "account not found", "asset not found".
embed-subtitles
by aviz85
"Burn subtitles onto videos using FFmpeg. Use for: hardcode subtitles, embed captions, video subtitling."
go-lint-audit
by gopherguides
WHEN: User wants to run linting on their Go project, understand lint findings, improve their golangci-lint configuration, or asks "what's wrong with my code?" from a linting perspective. WHEN NOT: Deep code quality audit (use go-code-audit), or auto-fixing lint issues (use /lint-fix command).
golang-concurrency-patterns
by bobmatnyc
"Go concurrency patterns for production services: context cancellation, errgroup, worker pools, bounded parallelism, fan-in/fan-out, and common race/deadlock pitfalls"
golang-cli-cobra-viper
by bobmatnyc
"Building production-quality CLI tools with Cobra command framework and Viper configuration management"
golang-http-frameworks
by bobmatnyc
"Go HTTP API development with net/http, Chi, Gin, Echo, and Fiber frameworks"
nextjs-core
by bobmatnyc
Core Next.js patterns for App Router development including Server Components, Server Actions, route handlers, data fetching, and caching strategies
git-workflow
by bobmatnyc
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
golang-observability-opentelemetry
by bobmatnyc
"Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog"
golang-database-patterns
by bobmatnyc
"Go database integration patterns using sqlx, pgx, and migration tools like golang-migrate"
example-framework-skill
by bobmatnyc
Example of a properly self-contained skill following all best practices
systematic-debugging
by bobmatnyc
"Systematic debugging methodology emphasizing root cause analysis over quick fixes"
bug-fix
by bobmatnyc
"Systematic workflow for verifying bug fixes to ensure quality and prevent regres..."
ux-audit-rethink
by mastepanoski
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
cognitive-walkthrough
by mastepanoski
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
nielsen-heuristics-audit
by mastepanoski
Evaluate UX/UI using Jakob Nielsen's 10 usability heuristics. Comprehensive audit of visibility, control, consistency, error prevention, recognition, flexibility, aesthetics, error recovery, and documentation.
vvvv-troubleshooting
by tebjan
Diagnoses and fixes common vvvv gamma errors in C# nodes, SDSL shaders, and runtime behavior. Use when encountering errors, exceptions, crashes, red nodes, shader compilation failures, missing nodes in the browser, performance issues, or unexpected behavior.
vvvv-debugging
by tebjan
"Set up debugging for vvvv gamma C# node projects -- generate VS Code launch.json and tasks.json configurations, attach debugger to running vvvv, configure Visual Studio debug profiles, and use debugging best practices. Use when setting up a debugger for vvvv, creating launch configurations, attaching to vvvv process, or troubleshooting breakpoints in C# nodes. Supports multiple launch configs for different test scenarios/patches."
vvvv-custom-nodes
by tebjan
"Helps write C# node classes for vvvv gamma — the [ProcessNode] pattern, Update() method, out parameters, pin configuration, change detection, stateless operation nodes, and service consumption via NodeContext (IFrameClock, Game access, logging). Use when writing a node class, adding pins, implementing change detection, accessing services in node constructors, or creating stateless utility methods. Requires [assembly: ImportAsIs]."