Coding standards, frameworks, refactoring, and code review (16.7K skills)
Use when a trusted bug or performance report needs reproduction and fix. Not for untrusted reports or scope beyond the named feature.
The English summary is being prepared. Showing the original description.
Use when the user says "simplify this diff" or asks for a compression pass over a change-set. Not for dead-code sweeps: use deslop.
The English summary is being prepared. Showing the original description.
Use when code mixes units, fixed-point precisions, scaling factors, rates, prices, shares, or conversions. Not for type-level unit modeling: use type-driven.
The English summary is being prepared. Showing the original description.
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.
The English summary is being prepared. Showing the original description.
Use when asked to explore the codebase to map structure, symbols, and dependencies. Not for a single file under 50 LOC: read it directly.
The English summary is being prepared. Showing the original description.
Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.
The English summary is being prepared. Showing the original description.
Use when modeling a domain, encoding a state machine, hardening APIs, making invalid states unrepresentable, or parsing instead of validating. Not for TypeScript: use typescript-best-practices.
The English summary is being prepared. Showing the original description.
Use when asked to build or review a CLI intended for coding agents and return flag-driven, pipeline-safe, idempotent design advice. Not for running or profiling a CLI: use control-cli.
The English summary is being prepared. Showing the original description.
Use when the user says greenfield this or rescue this codebase, names a field (dark, red, blue, or brown), or diagnoses a subsystem. Not for specs: use to-spec. Not for remote or irreversible changes.
The English summary is being prepared. Showing the original description.
Use when the user wants a clean Xcode rebuild by deleting DerivedData and build artifacts. Do not use for diagnosing a specific build error: use ios-build-fix.
The English summary is being prepared. Showing the original description.
Use when asked to run /clean-clean-cut to cut accumulated records and residue. Not for untracked or non-VCS changes, or branch/worktree cleanup: use git-cleanup.
The English summary is being prepared. Showing the original description.
Use when the user asks to simplify, clean, or refine code. Not for new abstractions or whole-codebase refactors.
The English summary is being prepared. Showing the original description.
Backend conventions and patterns. Use when working on API routes, dependency injection, or hexagonal architecture in the backend.
The English summary is being prepared. Showing the original description.
Database conventions and patterns. Use when working on database schemas, migrations, or data modeling.
The English summary is being prepared. Showing the original description.
Manage the kanban board. List, read, and close GitHub issues.
The English summary is being prepared. Showing the original description.
Checks the status of the repository
The English summary is being prepared. Showing the original description.
Check this project's memory notes against the repo, fix the ones that went false, and tidy the index, as one git commit you can revert. Checks only notes that are new or name a changed file; pass `all` to check every note. Costs one Sonnet call per 15 notes, plus one.
The English summary is being prepared. Showing the original description.
Diagnose tbh-meter problems — reader not attaching, AV/blocked state, slow calibration, missing or invalid runs. Use when debugging meter behavior or reading meter.log / live.json / raw run records / logs records (or the legacy runs.jsonl).
The English summary is being prepared. Showing the original description.
调研中国硕士研究生考试（考研）目标院校与专业的历年招生数据，评估择校爆冷/爆热、缩招、推免挤压、复试线虚低、专业课变更和复试风险，并给出冲稳保建议。适用于用户询问考研择校、院校难度、报录比、复试线、招生计划、统考名额、推免比例、拟录取分数、某校会不会爆、目标分数或需要导入自有 CSV/JSON 数据时。应先搜索公开网络和官方来源，确实找不到关键数据后再向用户索取补充材料；支持 Codex、Claude Code 和其他能读取 Skill Markdown 的 agent。
The English summary is being prepared. Showing the original description.
Freeze outside-the-repo state into one snapshot. Use when the work depends on the current state of a service, database, queue, third party, or live logs.
The English summary is being prepared. Showing the original description.
Build the thing the user can't specify, choices surfaced. Use when the user needs something to react to before they can choose.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
The English summary is being prepared. Showing the original description.
コードベースの不要なフォールバック・互換性コード・デッドコードを 3つの専門エージェント（scanner + historian + verifier）が協調して検出・安全性検証する監査スキル。 scanner が自律探索で候補を発見し、historian が git 履歴から時間軸の文脈を付与し、 verifier が「消してデグレしないか」を検証する。任意のリポジトリで実行可能。 Use when: コードのクリーンアップをしたい、技術的負債を可視化したい、 不要な互換性コードや deprecated コードを探したい、 リリース前に dead code を確認したい。 Triggers: "cruft", "code sweep", "dead code", "デッドコード", "不要なコード", "互換性コード", "fallback", "フォールバック", "deprecated", "技術的負債", "code audit", "コード監査", "cleanup", "クリーンアップ", "TODO整理"
The English summary is being prepared. Showing the original description.
Hook スクリプトを claude-code-plugin リポジトリの正しい構造に配置するスキル。 hook の構造検証、既存 hook との重複チェック、plugin.json 生成、marketplace.json 登録を行う。 Use when: hook をプラグインリポジトリに公開したい、hook を移動したい、hook をパッケージ化したい。 Triggers: "hook を公開", "hook publish", "hook をプラグインに追加", "PostToolUse hook を配置", "hook をコピー", "hook publisher"
The English summary is being prepared. Showing the original description.