Debugging
Find and fix bugs, error analysis
commit-creator
by Perdolique
Generate semantic commit messages following conventional commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when user mentions commit, commit message, conventional commits, semantic commits, git commit, stage changes, create commit. Supports monorepo package version tracking.
mcp-playwright
by janjaszczak
Automate browser flows and capture evidence (screenshots, console/network errors). Use for UI verification, repro steps, and end-to-end smoke tests.
systematic-debugging
by ederheisler
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
lint-build-fixer
by vajahath
"Used to systematically fix TypeScript build errors and ESLint linting issues. Triggers when asked to 'fix the build', 'resolve lint errors', 'fix type errors', or when build/lint failures are detected. Follows a strict priority: 1) Identify scripts, 2) Fix TS/Build errors first, 3) Verify & Commit build fix, 4) Fix Lint (Auto-fix first, then rule-by-rule), 5) Final Full Verification."
todo-list
by shadowcz007
智能待办事项管理技能。支持自然语言时间解析、事项记录与追踪、进度更新，数据持久化到本 skill 目录下 temp 的 Markdown；可通过 node scripts/time.js 与 node scripts/todo.js 调用。
react-hook-form-zod-shadcn
by Sortweste
Build forms in React. Use when the user needs to build or refactor forms in React.
systematic-debugging
by hrdtbs
A rigorous debugging protocol to find root causes before attempting fixes. Use this when encountering bugs, test failures, or unexpected behavior to avoid "thrashing" and random guessing.
flutter-ui-fix-from-qa
by Envy-7z
Fix Flutter UI issues based on QA screenshots (padding, spacing, alignment, dividers). Use when asked to match UI precisely without refactoring unrelated code.
change-writer
by dtsvetkov1
Generates clean, human-readable changelogs and release notes from git commits and file changes. Use when preparing for a release or summarizing recent work.
pdf-forge
by rendis
Use when building, extending or using pdf-forge multi-tenant PDF template engine with Typst
frontend-typescript
by hwatkins
Expert TypeScript development for frontend applications. Covers type safety, patterns, generics, utility types, and best practices. Use for any TypeScript code.
code-quality
by brixtonpham
"Code quality improvement: review, refactoring, debugging. Phases: review feedback, systematic refactoring, root cause debugging, verification. Capabilities: SOLID/DRY compliance, code smell detection, complexity reduction, bug investigation, verification gates. Actions: review, refactor, debug, verify, validate code. Keywords: code review, refactor, debug, SOLID, DRY, code smell, bug fix, root cause, verification, technical debt, extract method, test failure, completion claim. Use when: reviewing code changes, improving code quality, fixing bugs, reducing technical debt, validating before merge/commit."
api-design
by jamelna-apps
When the user mentions "API", "endpoint", "REST", "GraphQL", "route", "request", "response", "backend", or asks about designing web service interfaces.
chrome-debug
by pengelbrecht
This skill should be used when debugging web applications, diagnosing page errors, inspecting console output, or capturing screenshots of pages. It provides Chrome DevTools Protocol (CDP) automation via the chromectl.py script for collaborative or automated browser debugging.
commit-summary
by kennethkeim
Summarize git commits for a manager. Use when the user asks to summarize commits, create a status update, or prepare notes for their manager.
trust-and-recovery
by bfmcneill
Use when designing error handling, confirmation dialogs, undo functionality, or any interaction where user trust matters. Covers building confidence through predictability and graceful failure.
code-review-and-commit
by abpai
Review uncommitted Git changes for correctness, quality, and project convention alignment, then apply fixes and prepare a safe, atomic commit plan. Use when users ask to review code before committing, improve local changes, split work into logical conventional commits, or execute git add/git commit with clear staging boundaries.
kubeview-debug
by mikhae1
Debug and diagnose Kubernetes clusters using KubeView MCP server tools. Use when investigating cluster issues (pod crashes, deployment failures, service connectivity problems, node issues, resource constraints), performing cluster health checks, or troubleshooting any Kubernetes workload. Trigger phrases include "cluster health", "pod won't start", "CrashLoopBackOff", "service unreachable", "deployment stuck", "node pressure", "OOMKilled", "ImagePullBackOff".
fsharp-code-review
by bromanko
This skill should be used when the user asks to "review F# code", "fsharp code quality", "F# idioms check", "review my F#", "check code quality", or wants feedback on F# code patterns, idioms, Result handling, or module organization.
Skills
by gighive
For debugging, include what to check, where to check it, and what outcome to expect.
bcryptjs
by yusenthebot
Optimized bcrypt in plain JavaScript with zero dependencies, with TypeScript support. Compatible to 'bcrypt'.. Use when: From GitHub via jsDelivr: ; Callback<T>: (err: Error null, result?: T) => void ; ProgressCallback: (percentage: number) => void . NOT for: runtime application logic; package management (use npm/yarn).
elixir-development
by vircung
Modern Elixir idioms, functional patterns, testing strategies, and implementation best practices
git-commit
by bresends
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
test-generation
by Protagonistss
分析源代码并生成对应的单元测试用例。