patchwork

Pins CONTEXT.md capsules to preserve codebase intent during edits and refactors.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill patchwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patchwork
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/patchwork/skills/patchwork
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill patchwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Without guardrails, teams risk losing code intent, inconsistent terminology, and costly rework as code evolves. Patchwork keeps context anchored next to work so the agent maintains alignment with project standards.

Core Features & Use Cases

  • CONTEXT.md capsule rules: place a CONTEXT.md at the project root and read capsule boundaries before editing to preserve domain terms and intent.
  • Entry contract discipline: exports and signatures are surfaced through a defined entry point to prevent API drift.
  • WHY comments and change-scope controls: document rationale and constrain edits to guard rails.
  • Automatic capsule injection: inject ancestor CONTEXT.md chains for context continuity during tool-assisted tasks.
  • Tooling guidance: aligns with MCP search/read_context and the context-doctor to keep capsules healthy.

Quick Start

Create a CONTEXT.md at the capsule root and start applying the patchwork guardrails for all code tasks.

Frequently Asked Questions about patchwork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve codebase context and intent during refactoring?

To preserve codebase context during refactoring, pin a CONTEXT.md capsule beside your code work to anchor domain terms and intent. This prevents loss of project standards and avoids inconsistent terminology as your codebase evolves.

What are entry contracts in code review and why do they matter?

Entry contracts in code review surface exports and signatures through a defined entry point to prevent API drift. Enforcing entry contract discipline ensures that module boundaries remain stable and aligned with project standards during edits.

How do I manage context continuity for large codebases using MCP tooling?

Manage context continuity for large codebases by using MCP tooling to automatically inject ancestor CONTEXT.md chains. Aligning with MCP search and context-doctor keeps capsules healthy and preserves context during tool-assisted tasks.

What is the best way to constrain edit scope when debugging mid-sized codebases?

The best way to constrain edit scope when debugging is to apply change-scope controls and WHY comments. Documenting rationale and limiting edits to guardrails prevents unintended side effects across mid-sized to large codebases.

When do I need a CONTEXT.md file for my development process?

You need a CONTEXT.md file at your project root when working across mid-sized to large codebases where losing code intent is a risk. It enforces frontmatter rules, domain terms, and change-scope limits during writing, editing, and reviewing.