- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
debugger
by YPYT1
集合了所有的openclaw,claudecode,open等各个平台所有的skills
trpc
by ehyland
End-to-end typesafe APIs with tRPC
git:amend
by IKatsuba
Amend Commit - modifies the last commit with staged changes or new message
business-logic-review
by simplerick0
Review code for business logic correctness, edge cases, and alignment with requirements. Use for verifying feature implementations, catching logic errors, ensuring proper handling of business rules, and validating that code does what was intended.
react-patterns
by biruk741
React and React Native bug patterns and verification conditions. Covers hooks, state, effects, navigation, and async patterns.
code-review
by mishankov
Perform comprehensive software code reviews focused on correctness, regressions, security, reliability, performance, and test quality. Use when asked to review pull requests, commits, branches, patches, or source files and deliver prioritized findings with severity, concrete impact, and file/line references.
m06-error-handling
by lywa1998
"CRITICAL: Use for error handling. Triggers: Result, Option, Error, ?, unwrap, expect, panic, anyhow, thiserror, when to panic vs return Result, custom error, error propagation, 错误处理, Result 用法, 什么时候用 panic"
javascript-code-review
by TriNgo0108
Master JavaScript code review patterns including modern syntax, async/await, equality operators, memory leaks, and DOM manipulation. Use PROACTIVELY when reviewing JavaScript PRs.
issue
by keenranger
Create GitHub issue. Use when user asks to create issue, file bug, request feature, or says /issue.
checkpoint
by kl7sn
用户说 "ctx save" 时总结当前对话并按 ctx 规则存储;说 "ctx load" 时指导从 ctx 读回。也响应「保存对话」「创建 checkpoint」「插入 checkpoint」等表述。
dev-browser
by jtsang4
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
go
by kprsnt2
Best practices for Go development including idiomatic patterns, concurrency, and error handling.
debug-strategy
by jamelna-apps
When the user mentions "bug", "error", "not working", "broken", "crash", "fails", "issue", "problem", or asks why something doesn't work. Provides systematic debugging approaches.
mode-awareness
by jamelna-apps
When explicitly switching modes or when mode detection shows low confidence. Provides guidance on optimal approach for each detected mode (debugging, performance, feature, refactor, exploration, infrastructure).
basecamp-assistant
by nikhilbhansali
"Basecamp 4 assistant with a complete Python API client. Fulfill user requests by writing and executing Python code against BasecampClient. Use when users want to interact with Basecamp: managing projects, to-dos, messages, documents, schedules, card tables (Kanban), campfire chat, people, webhooks, templates, or any other Basecamp 4 feature. Triggers on: any mention of Basecamp, project management tasks referencing Basecamp data, or requests to read/write/update Basecamp resources."
error-handling
by ddaanet
Bash error handling rules and token-efficient exception patterns. Loaded when agents need error handling guidance for bash command execution.
git-commit
by totto2727-dotfiles
Analyzes git changes and creates granular commits with Conventional Commits format messages. Detects repository language pattern from recent commits. MUST ALWAYS be used when creating git commits, regardless of whether the user explicitly requests it or not.
receiving-code-review
by Cygnusfear
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
cpp-bug-tracer
by Nielk74
Investigates bugs in large, complex C++ codebases by progressively tracing execution paths from a natural language bug description. Uses a tree of subagents to decompose investigations. Use this skill whenever a user reports a bug or unexpected behavior in a C++ application and asks why something happens, why a feature doesn't work, what gets triggered when an action occurs, or why behavior differs between cases. Trigger for any question of the form "why does X work differently when Y" or "why can't I do Z in context W" or "what happens when the user does A" in a C++ project.
securing-ai-generated-code
by chrbailey
Reviews AI-generated code for security vulnerabilities before commit. Checks for injection flaws, privilege escalation, hardcoded secrets, insecure defaults, and missing input validation. Use when reviewing code written by AI coding agents, after code generation, or before committing AI-assisted changes.
accessibility-fundamentals
by slurpyb
Auto-invoke when reviewing JSX with interactive elements, forms, buttons, or navigation. Enforces WCAG compliance and inclusive design.
systematic-debugging
by Jackiexiao
(中文)Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
systems-analyst
by Tomlord1122
Systems analysis expert for understanding unfamiliar codebases, distributed architectures, and technical toolchains. Use when asked to investigate a system, survey how components interact, explain what a tool does, find gaps in an architecture, or produce a learning document about a technical domain.
devdocs-insights
by ab300819
Collect improvement insights from UI/UX reviews, document research, or external references, convert confirmed items into development requirements. Use when users have optimization suggestions, research findings, or want to improve based on external references. Triggers on keywords like "insights", "improvements", "optimize", "review findings", "research", "借鉴", "优化建议", "审查结果", "调研".