Sponsored by

Find leads on Reddit on auto pilot

Agent skills
debugging

Topic: debugging

23 skills in this topic.

e2e Run e2e and unit tests for Claude Inspector. Use after code changes to verify regressions.
kangraemin/claude-inspector 114
deploy Claude Inspector macOS 배포 스킬. 빌드(코드사이닝+공증) → GitHub Release → Homebrew cask 업데이트 전체 플로우. '배포', 'deploy', '릴리즈', 'release', '배포해', '출시' 등 배포 관련 요청 시 반드시 이 스킬을 사용한다.
kangraemin/claude-inspector 114
build Build and package Claude Inspector as a distributable Electron app (.dmg / .exe)
kangraemin/claude-inspector 114
troubleshooting Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
ChromeDevTools/chrome-devtools-mcp 32,738
memory-leak-debugging Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab.
ChromeDevTools/chrome-devtools-mcp 32,738
debug-optimize-lcp Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.
ChromeDevTools/chrome-devtools-mcp 32,738
chrome-devtools-cli Use this to skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
ChromeDevTools/chrome-devtools-mcp 32,738
chrome-devtools Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).
ChromeDevTools/chrome-devtools-mcp 32,738
a11y-debugging Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
ChromeDevTools/chrome-devtools-mcp 32,738
verification-before-completion Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.
CodingCossack/agent-skills-library 17
writing-skills Use when creating new skills, editing existing skills, or verifying skills work before deployment
CodingCossack/agent-skills-library 17
writing-plans Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
CodingCossack/agent-skills-library 17
brainstorming Collaborative design exploration that refines ideas into validated specs through iterative questioning. Use before any creative work including creating features, building components, adding functionality, or modifying behavior.
CodingCossack/agent-skills-library 17
using-superpowers Meta-skill enforcing skill discovery and invocation discipline through mandatory workflows. Use when starting any conversation to check for relevant skills before any response, ensuring skill-first workflow before proceeding.
CodingCossack/agent-skills-library 17
using-git-worktrees Git worktree–based workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.
CodingCossack/agent-skills-library 17
test-driven-development Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
CodingCossack/agent-skills-library 17
systematic-debugging Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
CodingCossack/agent-skills-library 17
subagent-driven-development Sequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in current session, when tasks need fresh subagent context to avoid pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based validation of each task before proceeding.
CodingCossack/agent-skills-library 17
requesting-code-review Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.
CodingCossack/agent-skills-library 17
receiving-code-review Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.
CodingCossack/agent-skills-library 17
finishing-a-development-branch Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.
CodingCossack/agent-skills-library 17
executing-plans Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
CodingCossack/agent-skills-library 17
dispatching-parallel-agents Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
CodingCossack/agent-skills-library 17