code-quality
3.9K
doc-add-simple-hash
markdown文档编辑时，为标题添加简单的哈希锚点，当用户提到添加简单哈希锚点时强制调用。
didi
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
3.8K
improve-code-quality
Analyze and improve code quality for any path in the monorepo. Use whenever the user asks to improve, audit, review, clean up, refactor, lint, or check code quality for a directory or file. Also trigger for requests about security review, performance optimization, robustness checks, dependency audits, or readability improvements. Activate for any mention of code quality, code health, code smells, tech debt, or cleanup tasks targeting a specific path. Even if the user just says "check this code" or "review crates/foo", this skill applies.
moonrepo
testing-security
code-quality
3.7K
python-cli-schema
Maintains the Python CLI argument schema, parser, validator, merger, and config-translation layer that mirrors the router config contract. Use when modifying CLI argument definitions, updating config validation rules, changing how CLI inputs are merged, or adjusting config translation between CLI and router formats.
vllm-project
testing-security
code-quality
3.6K
pr-review
Review code changes for quality, security, correctness, and design. Use when a feature branch is ready for review, before creating or updating a pull request, when asked to check code quality, review changes, look at a diff, or verify a branch is merge-ready. Also triggers on phrases like "review my code", "what do you think of these changes", or "is this ready to merge".
IBM
testing-security
code-quality
3.5K
erigon-seg-integrity
Run integrity checks on Erigon datadirs using the 'erigon seg integrity' command. Use this when the user wants to verify snapshot/segment file integrity or during the snapshot publishing process.
erigontech
testing-security
code-quality
3.5K
lint-check
Run pre-commit hooks and golangci-lint to verify code quality before finishing work
okteto
testing-security
code-quality
3.4K
code-execution
Use when a subtask is ready to implement and has a subtask JSON file with acceptance criteria and deliverables.
darrenhinde
testing-security
code-quality
3.4K
code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
darrenhinde
testing-security
code-quality
3.4K
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always
darrenhinde
testing-security
code-quality
3.4K
avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
aiming-lab
testing-security
code-quality
3.4K
test-before-ship
Use this skill when implementing a new feature or fixing a bug. Write or update tests before marking the task done. Never consider code complete without verifying it works through automated tests.
aiming-lab
testing-security
code-quality
3.3K
high-level-code-review
reviewing a change for semantic correctness, simplicity, design consistency, and completeness
stellar
testing-security
code-quality
3.3K
validating-a-change
comprehensive validation of a change to ensure it is correct and ready for a pull request
stellar
testing-security
code-quality
3.3K
review-and-simplify-changes
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
Dimillian
testing-security
code-quality
3.2K
code-review-expert
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
sanyuan0704
testing-security
code-quality
3.2K
token-audit
Audit Claude Code configuration to measure fixed-context token overhead and produce a prioritized action plan
FlorianBruniaux
testing-security
code-quality
3.2K
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
FlorianBruniaux
testing-security
code-quality
3.2K
atopile-skills
How to write and maintain `.claude/skills/*/SKILL.md` files: source-of-truth-first process, verification steps, and conventions.
atopile
testing-security
code-quality
3.2K
code-review
LLM-focused code review process for this repo: what to check, how to ground feedback in invariants/tests, and how to verify changes efficiently (including test-report.json).
atopile
testing-security
code-quality
3.1K
validate
Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".
agenticnotetaking
testing-security