Code Review
Automated code review and analysis
agentic-flow-builder
by P47Phoenix
Guide for building dynamic agentic flows using ReAcTree hierarchical decomposition and Anthropic's workflow patterns. This skill should be used when users want to create complex multi-step agent workflows with deterministic gates, business rules, and comprehensive audit trails.
ship
by open-horizon-labs
Deliver code to users. Optimize the path from merged code to working install. Use when execution is complete and you need to get changes into users' hands.
review-typescript-pull-request
by yonderlab
Expert PR review for TypeScript, Node.js, and React. Use when the user asks to review a pull request, review a PR, give PR feedback, or provide comprehensive context-aware feedback on changes. Triggers: "review this PR", "review pull request", "PR review", "feedback on this PR".
ask-owasp-security-review
by NavanithanS
Static security analysis for code, auditing for OWASP Top 10 risks. Triggers: "security audit", "is this secure", "check for vulnerabilities". Capabilities: - Static analysis of code snippets. - Mapping findings to OWASP Top 10 (2021). - Providing remediation code patterns.
retrospect
by cyberelf
This skill reviews the current chat session and GitHub Copilot instructions to identify user-reported issues that should become new lessons, detect violations of existing instructions, and update instructions accordingly to prevent future mistakes.
safe-update
by web3blind
Stateful and low-risk OpenClaw update workflow with precheck, backup, release-impact analysis, postcheck, auto-rollback, and cleanup. Use when user asks to safely update OpenClaw with rollback-ready backups and minimal manual steps.
development-process
by Kodria
Use when starting a new development task, resuming work, or when unsure which skill to invoke next - orchestrates the full development lifecycle from idea to merge
karpathy-guidelines
by caidanw
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
create-pull-request
by yonderlab
Create a pull request following the team's PR template and validation rules. Use when the user asks to create a pull request, create a PR, open a pull request, draft a PR, or prepare changes for review.
feature-dev
by huminglong
一个全面、结构化的特性开发工作流程，包含代码库探索、架构设计、质量审查和实现等专门阶段。在构建需要以下条件的新特性时使用：（1）在做出更改之前了解现有代码库，（2）通过系统性的提问澄清模糊的需求，（3）在实现之前设计周到的架构，（4）通过多维度的代码审查确保质量。非常适合涉及多个文件、需要架构决策、包含复杂集成或需求有些不明确的功能特性。
roadmap-phase-normalizer
by Jpkovas
Diagnose roadmap reality versus plan, identify abandoned or stale work, and normalize upcoming phases into execution-ready slices with explicit entry/exit criteria. Use when asked to check project roadmap status, find abandoned efforts, clean legacy dependency decisions, or rebuild next phases (roadmap, fase, abandonado, dependencias legadas, tech debt planning).
dependency-audit
by manastalukdar
Comprehensive dependency security and license audit
gh-issue-fix-pr
by brucehart
"Implement enhancements or fixes from one or more GitHub issues using the gh CLI. Use when a task requires: reading issues by number, creating a new branch, implementing changes, committing, opening a PR against main, and linking the issue(s) to the PR."
ask-security-sentinel
by NavanithanS
Pre-flight security checker. Scan for secrets and vulnerabilities.
requesting-code-review
by buildrtech
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
euler-vaults
by euler-xyz
Core guide for interacting with Euler Finance V2 protocol. This skill should be used when building DeFi integrations, managing lending positions, or understanding Euler architecture. Triggers on tasks involving lending, borrowing, collateral, liquidation, EVC, EVK, or core Euler operations. For specialized topics, see companion skills.
moai-alfred-code-reviewer
by AJBcoding
Enterprise systematic code review orchestrator with TRUST 5 principles, multi-language support, Context7 integration, AI-powered quality checks, SOLID principle validation, security vulnerability detection, and maintainability analysis across 25+ programming languages; activates for code reviews, quality standard validation, TRUST 5 enforcement, architectural audits, and automated review automation
ghe-thread-manager
by Emasoft
Use this skill when the user expresses ANY intent related to issue/thread management: - Switching issues: "let's work on X", "switch to #Y", "go to the auth issue" - Checking status: "what are we working on?", "current issue?", "status?" - Background work: "what's in background?", "any features ready?", "check progress" - Starting development: "implement X", "add feature", "fix bug Y", "build a..." - Joining reviews: "let me see the review", "check that feature", "join #X" - Pausing/resuming: "pause this", "come back later", "resume #X" - Stopping transcription: "stop tracking", "don't record this", "private mode" - Resuming last session: "what were we working on?", "resume last issue", "continue where we left off" - Any natural expression of wanting to change focus or check work status This skill interprets natural language - users should NOT memorize commands. For the full GHE workflow protocol, see skill: github-elements-tracking
github-elements-tracking
by Emasoft
This skill should be used when the user asks to "track work across sessions", "create an epic", "manage issue waves", "post a checkpoint", "claim an issue", "recover from compaction", "coordinate multiple agents", "update memory bank", "store large documents", or mentions GitHub Issues as persistent memory, multi-session work, context survival, agent collaboration, SERENA MCP memory, or project-level context. Provides complete protocols for using GitHub Issues as permanent memory that survives context exhaustion, with integrated SERENA MCP memory bank for project-level context and large document storage.
code-review
by otrebu
Expert code review specialist. Reviews for quality and intent alignment. Use immediately after writing or modifying code, or when user requests code review. Handles both uncommitted changes and targeted file reviews.
transformation-workflow
by hummbl-dev
Practical application guide for HUMMBL's 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes when to use each transformation, combination patterns, analysis templates, output formats, real-world examples, and common pitfalls. Essential for applying mental models effectively in problem-solving and analysis.
analyze-size
by otrebu
Analyze codebase size and language distribution using cloc. Use when user wants to understand codebase scale, primary languages, code composition, or assess project complexity. Provides total LOC, size category, language breakdown percentages, and key insights.
auth-route-protection-checker
by hopeoverture
This skill should be used when the user requests to audit, check, or generate authentication and authorization protection for Next.js routes, server components, API routes, and server actions. It analyzes existing routes for missing auth checks and generates protection logic based on user roles and permissions. Trigger terms include auth check, route protection, protect routes, secure endpoints, auth middleware, role-based routes, authorization check, api security, server action security, protect pages.
ghe-transition
by Emasoft
CHANGE phases in the GitHub Elements workflow. Closes current thread and opens next phase thread. This is a PHASE CHANGE operation, not just saving progress. USE THIS SKILL WHEN: - User says "transition to TEST" or "move to REVIEW" - User says "I'm done with DEV, start TEST" or "DEV complete" - User says "advance to next phase" or "close this phase" - User says "demote to DEV" (from TEST or REVIEW) - User says "tests pass, ready for review" - User says "merge this" (after REVIEW PASS) - User explicitly wants to END current phase and BEGIN next DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to SAVE progress but CONTINUE working (use ghe-checkpoint) - User wants reports (use ghe-report) - User is not ready to END current phase IMPORTANT: This CLOSES current thread and OPENS next thread. Use ghe-checkpoint if you just want to save progress without changing phases. EXAMPLES: <example> Context: DEV work complete, ready for testing user: "I'm done with DEV, transition to TEST" assistant: "I'll use ghe-transition to close DEV and open TEST thread" </example> <example> Context: All tests pass, ready for review user: "Tests pass, move to REVIEW" assistant: "I'll use ghe-transition to close TEST and open REVIEW thread" </example> <example> Context: Structural issues found in TEST user: "This needs structural changes, demote to DEV" assistant: "I'll use ghe-transition to demote from TEST back to DEV" </example> <example> Context: REVIEW passed, ready to merge user: "REVIEW passed, merge it" assistant: "I'll use ghe-transition to complete the workflow and merge" </example>