By NeoLabHQ
Introduce codebase and PR review commands and skills using multiple specialized agents.
Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.
Use this agent to rate each changed file based on 2 criteria and output final list of files that require most attention.
Use this agent to rate each changed file based on 2 criteria and output final list of 10 files that require most attention.
Use this agent to rate each changed file based on 4 criteria and output final list of 10 files that require most attention.
Use this agent to build "story" of this change, that will be used to review it by human reviewer. Story must explain what this change tries to achive, what risks it introduces and how it solve them.
Review your local uncommitted working-tree changes (git diff plus untracked files) and return actionable improvement suggestions. Use before committing, when nothing has been pushed yet.
Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.
This skill should be used when need prioritize what changed code in repository human must review.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Advanced context engineering techniques and patterns for Claude Code, OpenCode, Cursor, Antigravity and more.
Quick Start · Plugins · Github Action · Reference · Docs
A hand-crafted collection of advanced context engineering techniques and patterns with minimal token footprint, focused on improving agent result quality and predictability.
The marketplace is based on prompts our company's developers have used daily for a long time, supplemented by plugins from benchmarked papers and high-quality projects.
Updates from key releases:
Open Claude Code and add the Context Engineering Kit marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit
This makes all plugins available for installation, but does not load any agents or skills into your context.
Install any plugin — for example, reflexion:
/plugin install reflexion@NeoLabHQ/context-engineering-kit
Each installed plugin loads only its specific agents, commands, and skills into Claude's context.
Run the vercel-labs/skills command in your terminal:
npx skills add NeoLabHQ/context-engineering-kit
You can pick which skills and agents to install.
You can use OpenSkills to install skills by running the following commands:
npx openskills install NeoLabHQ/context-engineering-kit
npx openskills sync
First Principles Framework (FPF) for structured reasoning using workflow command pattern. Implements ADI (Abduction-Deduction-Induction) cycle via propose-hypotheses workflow with fpf-agent for hypothesis generation, logical verification, empirical validation, and auditable decision-making. Includes utility commands for status, query, decay, actualize, and reset.
npx claudepluginhub neolabhq/context-engineering-kit --plugin reviewComprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
Review pull requests with structured analysis and approve with confidence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.