Code Review
Automated code review and analysis
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
market-research
by dmend3z
This skill enables Claude to conduct comprehensive market research, including customer interviews, competitor analysis, and social media listening. Use it to understand customer needs, identify market gaps, and inform marketing strategy.
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology
review-gate
by troykelly
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
documentation-audit
by troykelly
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
comprehensive-review
by troykelly
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
big-idea-development
by dmend3z
"This skill develops a powerful marketing message using Todd Brown's E5 methodology. It guides users through market sophistication analysis, unique mechanism discovery, and creating a compelling big idea for their campaign. Use when you need to craft a unique and persuasive marketing angle. Keywords: big idea, marketing message, E5 methodology, unique mechanism, value proposition."
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
project-status-sync
by troykelly
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
security-audit
by mgd34msu
"Load PROACTIVELY when task involves security review, vulnerability assessment, or hardening. Use when user says \"check for security issues\", \"audit for vulnerabilities\", \"scan for secrets\", \"review auth security\", or \"check OWASP compliance\". Covers authentication and session security, authorization and access control, input validation and injection prevention, data protection and encryption, dependency vulnerability scanning, API security (CORS, rate limiting, headers), and infrastructure hardening. Produces structured reports with severity ratings."
cetus-clmm-sdk-skill
by RandyPen
Guides developers through using Cetus CLMM TypeScript SDK for liquidity management, pool operations, swaps, and reward collection. Use when working with Cetus Protocol's Concentrated Liquidity Market Maker (CLMM) or when the user mentions Cetus SDK, CLMM, liquidity pools, or DeFi on Sui.
review
by chanmuzi
Review PR comments, discuss improvements, and reply with resolution status
makefile-best-practices
by plinde
Best practices for creating self-documenting Makefiles with auto-generated help. Use when creating or modifying Makefiles to ensure they follow conventions for discoverability and maintainability.
vibe-code-health-check
by FuzulsFriend
Scans any codebase and grades it A through F across 6 health dimensions (security, error handling, code structure, performance, deployment readiness, UX basics). Use when asked to "check my code", "audit my project", "is my code ready to ship", "review my codebase", "health check", "code quality check", "is my app secure", "vibe check my code", "scan my project", or "what is wrong with my code". Takes a codebase path and returns a scored report card with plain-English fixes.
error-recovery
by mgd34msu
"ALWAYS load before starting any task. Defines systematic recovery procedures when things go wrong during execution. Covers tool failures, build errors, test failures, type errors, and unexpected runtime results. Includes tiered escalation (retry, fallback, memory-informed diagnosis, orchestrator escalation) and post-recovery logging to prevent recurrence."
code-review
by mgd34msu
"Load PROACTIVELY when task involves reviewing code, auditing quality, or validating implementations. Use when user says \"review this code\", \"check this PR\", \"audit the codebase\", or \"score this implementation\". Covers the 10-dimension weighted scoring rubric (correctness, security, performance, architecture, testing, error handling, type safety, maintainability, accessibility, documentation), automated pattern detection for anti-patterns, and structured review output with actionable findings."
check-skill-conflicts
by plinde
This skill should be used when checking for naming conflicts between local skills (~/.claude/skills) and plugin-provided skills (~/.claude/plugins). Use to identify duplicate or similarly named skills that may cause inconsistent agent behavior.
fullstack-feature
by mgd34msu
"Load PROACTIVELY when task involves building a complete feature across multiple layers. Use when user says \"build a feature\", \"add user profiles\", \"create a dashboard\", or any request spanning database, API, UI, and tests. Orchestrates multi-agent work sequentially: schema and migrations, API endpoints, UI components, tests, and review. Handles dependency ordering and cross-layer type sharing."
self-review
by motiful
"Run a 4-pillar, 6-dimension alignment audit on the current project. Checks design currency, executes artifact verification, detects skill deposits. Use when the user says \"self-review\", \"审视一下\", or \"audit\". Report-only — never auto-fix."
commit
by chanmuzi
Create a git commit following project conventions
accessibility-audit
by mgd34msu
"Load PROACTIVELY when task involves accessibility compliance or inclusive design. Use when user says \"check accessibility\", \"audit for WCAG\", \"fix screen reader issues\", \"add keyboard navigation\", or \"check color contrast\". Covers WCAG 2.1 AA compliance across semantic HTML, ARIA patterns, keyboard navigation, screen reader support, color contrast ratios, form accessibility, media alternatives, and focus management. Produces structured audit reports with severity ratings."
cross-domain-thinking
by legacybridge-tech
Structured methods for finding connections across disciplines. Use when exploring how concepts from one field illuminate another, seeking novel applications, or analyzing structural similarities between domains.
plugin-research
by BitYoungjae
"Neovim plugin ecosystem research. Use for: version compatibility, GitHub issues, breaking changes, plugin alternatives. Provides systematic investigation patterns for plugin-related problems."