Debugging
Find and fix bugs, error analysis
secrets-handling
by yanko-belov
Use when working with API keys, passwords, or credentials. Use when asked to hardcode secrets. Use when secrets might leak.
scm
by mauromedda
Guide for effective source control management with Git following modern best practices. Covers branching strategies, commit hygiene, PR workflows, and team collaboration patterns. Triggers on "git", "source control", "version control", "branching", "merge", "rebase", "git workflow", "pull request", "commit message", "git history", "git conflict", "git stash", "git cherry-pick", "git bisect", "git blame", "git log", "git diff", "git reset", "git checkout", "git switch", "git restore", "git tag", "git remote", "git fetch", "git pull", "git push", "git branch", "conventional commits", "squash", "force push", "git hooks", "pre-commit", "commit-msg", "gitignore", "git submodule", "git worktree", "feature branch", "trunk based", "git flow", "github flow", "commit and push", "commit changes", "push changes", "push to remote", "commit this", "commit these", "make a commit", "create commit". PROACTIVE: MUST invoke when performing complex Git operations or setting up workflows.
idempotency
by yanko-belov
Use when creating mutation endpoints. Use when trusting frontend to prevent duplicates. Use when payments or critical operations can be repeated.
separation-of-concerns
by yanko-belov
Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.
SKILL_NAME
by dtsong
TRIGGER_DESCRIPTION. Use when USER_CONTEXT. Covers CAPABILITIES.
auth-patterns
by yanko-belov
Use when implementing authentication. Use when storing passwords. Use when asked to store credentials insecurely.
collaborating-with-gemini
by GuDaStudio
Delegates coding tasks to Gemini CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSION_ID.
race-conditions
by yanko-belov
Use when multiple operations access shared state. Use when order of operations matters. Use when "it works most of the time" but occasionally fails mysteriously.
git-conventions
by vendeesign
"Guide automatique pour les opérations git. Activer quand Claude exécute des commandes git (commit, branch, push, merge, rebase, PR) en dehors de /codebloom:push. Couvre : conventional commits, nommage de branches, messages de PR, et garde-fous contre les opérations destructives. Ne pas charger si /codebloom:push est active (elle intègre déjà ces conventions)."
code2wiki
by woaillr-crypto
为大型后端项目生成和维护面向业务的 Business Context Layer（业务语义层 / 项目知识地图）。当需要总结、梳理、文档化、wiki 化、构建上下文、创建领域 skill、提升 LLM 对既有后端代码库的理解时使用——尤其适用于 10w+ 行、50w+ 行这类需求主要由业务驱动而不是技术模块驱动的系统。支持 Java/Spring、Kotlin（Spring/Ktor）、Python（Django/FastAPI/Flask）、Go（Gin/Echo/gRPC）、TypeScript/JavaScript（NestJS/Express）等多种后端栈；扫描器自动识别项目语言，混合语言 Monorepo 会并行扫描所有命中插件。也适用于多级业务域目录、项目知识地图、API/Database/Code Entrypoint 映射、风险清单、分层上下文（L0/L1/L2/Source）建设等任务。
next-best-practices
by fellipeutaka
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
faion-backend-systems
by faionfaion
"Systems backends: Go, Rust, databases, caching."
react-anti-patterns
by joacod
Introduce React anti-patterns and common mistakes into existing React codebases for training, review, or teaching. Use when asked to intentionally degrade React performance or code quality while keeping apps functional, or to generate anti-pattern examples for junior developer education.
Clean Code Skill for Node.js/TypeScript
by DoubleslashSE
```
solid
by fellipeutaka
Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.
requirements-clarification
by DoubleslashSE
Requirements clarification for TDD. Use BEFORE RED phase to understand WHAT to test. Asks targeted questions to uncover ambiguities, edge cases, and acceptance criteria.
sentry-issue-resolver
by Arctuition
"Analyze and resolve Sentry issues by fetching detailed issue information, performing deep root cause analysis, and providing actionable solutions. Use when the user asks to: (1) Analyze a Sentry issue, (2) Debug or investigate a Sentry error, (3) Fix a Sentry issue, (4) Get root cause analysis for application errors, (5) Resolve Sentry alerts. Works with Sentry URLs to fetch stack traces, error context, and event data."
suggest-performance-fix
by kjgarza
Identify performance issues and bottlenecks suggesting optimizations a senior developer would recommend. Use when user mentions performance/optimization/speed issues, asks "why is this slow?" or similar questions, code contains obvious performance anti-patterns (N+1 queries, unnecessary loops, etc.), user works on performance-critical code paths, performance profiling shows bottlenecks, or large data processing or database operations detected.
error-debugger
by Toowiredd
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference. Use when user says "debug this", "fix this error", "why is this failing", or when error messages appear like TypeError, ECONNREFUSED, CORS, 404, 500, etc.
development-workflow
by DoubleslashSE
General .NET development workflow patterns. Use when implementing features, fixing bugs, or refactoring code.
testing-builder
by Toowiredd
Automatically generates comprehensive test suites (unit, integration, E2E) based on code and past testing patterns. Use when user says "write tests", "test this", "add coverage", or after fixing bugs to create regression tests. Eliminates testing friction for ADHD users.
secure-node-typescript
by joacod
'Write secure-by-default Node.js and TypeScript applications following security best practices. Use when: (1) Writing new Node.js/TypeScript code, (2) Creating API endpoints or middleware, (3) Handling user input or form data, (4) Implementing authentication or authorization, (5) Working with secrets or environment variables, (6) Setting up project configurations (tsconfig, eslint), (7) User mentions security concerns, (8) Reviewing code for vulnerabilities, (9) Working with file paths or child processes, (10) Setting up HTTP headers or CORS.'
content-reflection
by drshailesh88
Pre-publication quality assurance for cardiology thought leadership content. Use AFTER any content is drafted to evaluate scientific rigor, voice authenticity, positioning alignment, audience calibration, and credibility risk. Provides structured critique with specific revision suggestions. Works on any content type—tweets, threads, newsletters, editorials, video scripts.
changelog-writer
by peopleforrester
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.