Code Review
Automated code review and analysis
process-review
by desplega-ai
Process review comments in a file after user finishes reviewing in file-review GUI. Extracts HTML comment markers, guides Claude through addressing each comment interactively, and removes resolved markers.
ln-621-security-auditor
by levnikolaevich
Security audit worker (L3). Scans codebase for hardcoded secrets, SQL injection, XSS, insecure dependencies, missing input validation. Returns findings with severity (Critical/High/Medium/Low), location, effort, and recommendations.
Security Engineer Skill
by wasintoh
Next.js Security: https://nextjs.org/docs/app/building-your-application/configuring/security
🔧 Debug Protocol Skill
by wasintoh
```
josh-braun-copywriting
by sachacoldiq
Josh Braun's 5 cold email writing principles plus personalization best practices. Use when refining email copy, improving message quality, or reviewing outreach for common mistakes.
ha-merge-queue
by home-assistant
Finds open Home Assistant pull requests that are genuinely ready to merge, checking CI, the merge-gate statuses, code-owner approval, merge conflicts, requested changes and unresolved review threads. Use when looking for PRs to merge, doing merge-queue triage, or asking for "quick wins" from the open PR backlog.
visualiser-performance
by event-catalog
React Flow performance rules and review checklist for the @eventcatalog/visualiser package. Automatically applies when making changes to any file under packages/visualiser/. Use this skill to audit, review, or implement visualiser code with performance in mind.
openspec-archive-change
by PBH-BTN
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
code-review
by agno-agi
Code review assistance with linting, style checking, and best practices
code-review
by kyegomez
Perform comprehensive code reviews focusing on best practices, security vulnerabilities, performance optimization, and maintainability
openspec-archive-change
by PBH-BTN
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
go-performance
by caarlos0
Analyze and optimize Go program performance. Use when asked to profile Go code, find performance bottlenecks, analyze memory allocations, detect memory leaks, write benchmarks, or optimize CPU/memory usage.
go-doc
by caarlos0
Get documentation for any Go library using go doc. Use when asked about Go package documentation, API reference, function signatures, or how to use a specific Go library/package.
clinical-decision-support-documents
by jaechang-hits
"Guidelines for generating clinical decision support (CDS) documents: patient cohort analyses (biomarker-stratified outcomes) and treatment recommendation reports (GRADE-graded evidence). Covers document structure, executive summary design, evidence grading (GRADE 1A–2C), statistical reporting (HR, CI, survival), and biomarker integration. Use when creating pharmaceutical research documents, clinical guidelines, or regulatory submissions."
telnyx-account-java
by team-telnyx
Manage account balance, payments, invoices, webhooks, and view audit logs and detail records. This skill provides Java SDK examples.
difit
by yoshiko-pg
After completing the requested implementation, use the difit command to ask the user for a code review.
claude-config-advisor
by chujianyun
审查或设计 Claude Code 项目配置。用于用户提到 .claude、CLAUDE.md、Claude 配置文件、项目级 Claude 自定义配置、配置结构是否合理、该创建哪些配置文件，或希望从零规划 Claude 配置时使用。默认先审查或诊断，再给方案；只有用户明确要求时，才进一步输出推荐结构或样例文件。
cran-extrachecks
by posit-dev
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback. Covers documentation requirements, DESCRIPTION field standards, URL validation, examples, and administrative requirements.
paper-revision
by lingzhi227
Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
related-work-writing
by lingzhi227
Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.
code-debugging
by lingzhi227
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
atdd-team
by swingerman
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a three-agent team (spec-writer, implementer, reviewer) through a five-phase ATDD workflow: spec writing, spec review, pipeline generation, implementation, and post-implementation review. Supports extending an existing team with ATDD roles without replacing current teammates.
docs-writer
by google-gemini
Always use this skill when the task involves writing, reviewing, or editing
pulseverifier
by FStarLang
Use fstar.exe to verify Pulse code and interpret the errors reported