bump-plugin
01NeoLabHQ/context-engineering-kit
Command Claude Code
Bump changed plugin and marketplace version.
NeoLabHQ/context-engineering-kit
Command Claude Code
Bump changed plugin and marketplace version.
NeoLabHQ/context-engineering-kit
Agent Claude Code
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.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent to rate each changed file based on 2 criteria and output final list of files that require most attention.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent to rate each changed file based on 2 criteria and output final list of 10 files that require most attention.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent to rate each changed file based on 4 criteria and output final list of 10 files that require most attention.
NeoLabHQ/context-engineering-kit
Agent Claude Code
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.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when analyzing existing codebase features, tracing execution paths, mapping architecture, identifying files affected by proposed changes, or understanding integration points for new development.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, or for reviwing pull request changes.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent at the END of an implementation phase to verify the phase's implementation against the task's acceptance criteria AND review code quality. Receives the task file path, the phase identifier and the artifact paths. Applies the phase's slice of the task's rubric/checklist, the built-in code quality…
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when implementing a single step of a task. Receives the task file path AND that step's sub-task file path. Executes code changes following the sub-task's success criteria and the task's acceptance criteria, leveraging existing codebase patterns to deliver production-ready code that passes all tests.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when reviewing local code changes or pull requests to understand the historical context of modified code, including past issues, patterns, and lessons learned. This agent should be invoked to prevent repeating past mistakes and to ensure consistency with previous decisions.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when evaluating implementation artifacts against an evaluation specification produced by the meta judge. Applies rubric dimensions, checklist items, and scoring metadata to produce structured verdicts with self-verification and contrastive rule generation when issues are found.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when generating evaluation rubrics, checklists, criteria, metrics, and weights for a user prompt BEFORE implementation begins. Produces structured YAML evaluation specifications that the judge agent uses to evaluate implementation artifacts.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when researching unknown technologies, libraries, frameworks, and dependencies to gather relevant resources and documentation for implementation tasks. Creates reusable skills that all agents can leverage.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when synthesizing research findings, codebase analysis, and business requirements into architectural solutions for task specifications.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when breaking down architecture into implementation steps with success criteria, dependencies, and risk assessment, and reorganizing those steps for maximum parallel execution. Transforms architectural blueprints into executable, parallelized task sequences written as per-step sub-task files grouped…
NeoLabHQ/context-engineering-kit
Agent Claude Code
Creates and maintains comprehensive, accessible technical documentation by transforming complex concepts into clear, structured content that helps users accomplish their tasks.
NeoLabHQ/context-engineering-kit
Agent Claude Code
Use this agent when you need to review local code changes or a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or tests updated, to ensure tests adequately cover new functionality and edge cases.
NeoLabHQ/context-engineering-kit
Skill Claude CodeCodex
Reconcile the project's FPF state with recent repository changes.
NeoLabHQ/context-engineering-kit
Skill Claude CodeCodex
Your role is to create a draft task file that exactly matches the user's request.
NeoLabHQ/context-engineering-kit
Skill Claude CodeCodex
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: