Debugging
Find and fix bugs, error analysis
code-analysis
by Protagonistss
代码质量与复杂度等静态分析能力，提供改进建议与报告。
fsharp-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve F# tests", "review tests", "test quality", "testing audit", or wants analysis of F# test suites for coverage gaps, edge cases, and testing best practices.
react-best-practices
by yonderlab
Apply React best practices when writing or reviewing React code. Use when building components, reviewing PRs, refactoring React code, fixing performance issues, debugging re-renders, structuring state and data flow, converting useEffect to loaders, building forms, or asking "how should I structure this component".
fusion-skill-self-report-bug
by equinor
Capture Fusion skill workflow failure context and guide a draft-first bug reporting flow with explicit confirmation before any GitHub mutation.
pr
by keenranger
Create GitHub pull request. Use when user asks to create PR, open pull request, or says /pr.
elixir-ecto
by hwatkins
Expert Ecto patterns for Elixir — changesets, Multi, composable queries, migrations, optimistic locking, multi-tenancy, and railway-oriented programming with with. Use when working with databases or data validation in Elixir.
remote
by Protagonistss
远程仓库管理技能 - 智能推送、拉取和多仓库同步。用于安全推送、智能拉取、同步分支或管理多个远程仓库。
frontend-react-router-best-practices
by Emerson1337
React Router performance and architecture patterns. Use when writing loaders, actions, forms, routes, or working with React Router data fetching. Triggers on tasks involving React Router routes, data loading, form handling, or route organization.
test-driven-development
by ederheisler
Use when implementing any feature or bugfix, before writing implementation code
prompt-optimizer
by gn00678465
Analyze and optimize user prompts through systematic deconstruction and framework-based reconstruction. Use when users request prompt improvement, optimization, refactoring, or restructuring. Triggers include "optimize this prompt", "improve this instruction", "refactor this prompt", "make this clearer", "restructure this prompt", or when analyzing poorly-structured prompts. This skill analyzes prompts for ambiguity, applies proven frameworks (B.R.O.K.E, T.R.A.C.E, C.L.E.A.R, etc.), and outputs high-precision, unambiguous prompts.
git-commit-message-follow-project-convention
by zetavg
"Read this skill before creating any git commit to ensure the commit message matches the project's established patterns. Triggers on: git commit, /commit, creating commits, or any task that results in a git commit."
Visualization & Interpretability
by sovr610
This skill should be used when the user asks to "visualize activations", "plot spike rasters", "show attention heatmaps", "visualize workspace", "plot reasoning traces", "create t-SNE embeddings", "interpret model decisions", "visualize HTM patterns", "show neuromodulator levels", "plot training curves", "create activation maps", "visualize feature maps", "explain predictions", "debug model behavior visually", or needs guidance on visualization, interpretability, or explainability tooling for the brain_ai system.
pr-review
by aivokone
Use FIRST for any PR/code review work — checking feedback, reading CR comments, responding to reviewers, addressing review bot or human comments, or preparing commits on a PR. Collects feedback from ALL sources (conversation, inline, reviews) to prevent the common failure of missing inline feedback. Start with check-pr-feedback.sh, then reply inline where needed and summarize with one Fix Report.
wagmi
by 0xSardius
React hooks for Ethereum and EVM blockchain interactions using Wagmi v3. Use when building React or Next.js apps with wallet connections, contract reads/writes, or blockchain state. Triggers on useAccount, useConnect, useContractRead, useContractWrite, WagmiProvider, ConnectKit, RainbowKit, or any React blockchain hooks. Do NOT use for Node scripts or non-React code (use viem skill instead).
google-golang-style
by meysam81
Enforces Google's official Go style guide when writing or editing Go (.go) files. Use this skill BEFORE creating, modifying, or reviewing any Go code. Covers naming (packages, receivers, variables, repetition avoidance), error handling (structure, wrapping, strings, sentinel errors), imports (grouping, renaming, blank imports), code organization (package size, file structure), and documentation (doc comments, godoc conventions). Trigger on any Go code task — new files, refactors, code reviews, or architecture decisions involving Go packages.
mcp-status
by fancy-bread
MCP Status
swiftui-scroll-animation
by jlreyes
Diagnoses scroll and animation jank in SwiftUI macOS/iOS apps using a frame-first workflow. Covers interaction windowing, severity buckets, cascade analysis, per-frame attribution, root cause clustering, and a final report template. Requires the claude-instruments skill for trace export and schema reference.
a11y
by politician
Expert web accessibility auditing + remediation for French RGAA 4.1.2 and WCAG 2.1.---
hotfix-workflow
by IHKREDDY
Rapid hotfix branch creation, fix application, and PR to main
product-requirements
by vilin1927
Generate comprehensive Product Requirements Documents (PRDs) through structured analysis and collaborative refinement. Use when planning new products, features, or major system changes.
effective-testing
by ab22593k
"A comprehensive methodology for highly effective, human-centered software testing. Use this skill when you need to: (1) Design a test strategy for a complex product, (2) Perform exploratory testing using Session-Based Test Management (SBTM), (3) Identify potential bugs using advanced oracle heuristics (FEW HICCUPS), (4) Report bugs with high business significance, (5) Perform prospective testing on requirements/designs, or (6) Supervise AI-generated work. Trigger this skill whenever 'testing', 'quality assurance', 'bug hunting', 'test strategy', 'automation traps', or 'risk analysis' are mentioned."
accessibility
by iulspop
Audits components and pages for WCAG accessibility issues and suggests fixes. Use when building new UI, reviewing components for a11y compliance, or fixing reported accessibility bugs.
backend-principle-eng-cpp-pro-max
by PrakharMNNIT
"Principal backend engineering intelligence for C++ systems and performance-critical services. Actions: plan, design, build, implement, review, fix, optimize, refactor, debug, secure, scale backend code and architectures. Focus: correctness, memory safety, latency, reliability, observability, scalability, operability."
git
by Alicoder001
Conventional Commits standard for consistent commit messages. Use when committing code, reviewing commit history, or setting up git workflows. Includes commit types, scopes, and breaking change format.