Discover research debugging skills, compare source repositories and read the instructions for each workflow.
Fast environment briefing for agents and subagents. Use at session start to learn OS/shell, container/WSL/VM status, git repo + upstream + dirty state, Python venv status/locations, markdown folders to read, an...
comprehensive project analysis identifying issues, missing documentation, and improvement opportunities. use when reviewing codebase health, onboarding to existing project, or conducting code quality assessment...
Find, triage, and fix bugs with or without user input. Autonomously scan codebases, produce an issues list, implement a fix, create a fix branch, commit via semantic-commit, and open a PR with gh.
Analyze test coverage, identify gaps, suggest strategic test cases. Use when writing features, after bug fixes, or during test reviews. Ensures comprehensive coverage without over-testing.
Analyze test suites for speed bottlenecks, redundancy, and DRY violations. Use when tests are slow, duplicated, or need refactoring.
Perform exploratory QA testing on web applications using Playwright. Navigate flows, analyze pages, find issues, and generate actionable reports with evidence.
Debug API 500 errors and unexpected responses. Use when mobile apps get server errors, when API returns wrong data, or when investigating failed requests. Checks server logs, common error patterns, and Prisma q...
Debug web app by capturing and analyzing console errors using Chrome DevTools MCP
Systematic debugging approach for identifying and fixing issues. Use when debugging, troubleshooting errors, or asking about bugs and problems.
Provides systematic code review with focus on quality, security, and best practices. Use when reviewing code, doing PR reviews, or asking for code feedback.
Guidelines and checklist for thorough code review.
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging fai...
Debug errors, trace bugs, find root causes. Investigate why code fails, trace execution paths, troubleshoot unexpected behavior, find why functions return wrong values. NOT for exploring unfamiliar code (use ex...
Runs Playwright E2E tests with smart targeting by app and feature, supports multiple environments (local/staging/production), and can generate new E2E test files. This skill should be used when running E2E test...
Verifies system health across all apps, edge functions, and database connectivity. This skill should be used for quick deployment verification, debugging service issues, daily operations checks, or before/after...
Uses ast-grep to find patterns and analyze code for refactoring. Use when planning refactors, finding deprecated API usage, migrating code, or analyzing code quality before changes. For simple code search, use...
Claudeを使った多角的コードレビュー。セキュリティ、パフォーマンス、保守性、設計の4観点で並列分析。 Use for: "レビューして", "コードレビュー", "多角的に見て", "4観点でレビュー"
Professional code review for quality, security, and best practices. Use when reviewing pull requests, code changes, or when asked to review code quality.
Semantic code search using Mantic. Use when exploring codebases, finding feature implementations, understanding component functionality, locating definitions/references, or mapping architectural patterns. Use M...
Use when working with Ruby metaprogramming features including dynamic method definition, method_missing, class_eval, define_method, and reflection.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Debug React component issues including TypeScript types, props, state management, hooks, and rendering problems. Use when troubleshooting component not rendering, prop errors, state not updating, hook issues, o...
Self-diagnostic debugging - Agent decides diagnostic approach. Auto-activates on "bug", "error", "debug", "不work", "壞掉" keywords. AMP principle: Think > Follow - Agent writes own debug tools.
Updates Aaron's Core Memory (CLAUDE.md) with session notes, project status, and development patterns
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.