Developer Context Compressor Kit

Free local-first shell bundle that gives AI coding assistants (Claude Code, Cursor, Copilot Chat) the repo context they need before touching unfamiliar code: a project map, an LLM handoff brief, and a bounded change-risk packet — generated in one command, no accounts, no cloud calls.

Local-first shell bundle for turning a repository into three bounded markdown artifacts:

1. project-map.md
2. llm-handoff.md
3. change-risk.md

Also hand-writing prompts for your AI assistant? → Prompt Starter Pack Premium ($9) — 40 battle-tested templates for code review, debugging, architecture decisions, and AI-agent design, in the same "one command, no fuss" spirit as this kit.

What It Does

• scripts/repo_map.sh scans a repo root and emits a shallow project map.
• scripts/llm_handoff.sh turns that map into an agent-ready orientation brief.
• scripts/change_risk.sh emits a bounded blast-radius and test checklist.
• scripts/packet_bundle.sh runs all three in one command.

Quick Start

After cloning the public repo, enter it once:

cd developer-context-compressor-kit

Run the full packet on the cloned kit itself:

make bundle

Verify the shipped fixture-backed regression checks before using the kit on another repo:

make check

Run the packet on another repo:

make bundle-target REPO=/path/to/repo

Run the packet on another repo with explicit target paths for the change-risk section:

make bundle-target \
  REPO=/path/to/repo \
  TARGETS="path/to/file1 path/to/file2"

make bundle-target is a repo-local shorthand for ./scripts/packet_bundle.sh /path/to/repo <target...>. Use it when the repo you want to inspect is not the DCCK clone itself.

Concrete Python example from an outside repo:

make bundle-target \
  REPO=/tmp/dcck-requests-targeted \
  TARGETS="src/requests/sessions.py tests/test_requests.py"

Concrete Rust example from an outside repo:

make bundle-target \
  REPO=/tmp/dcck-ripgrep-targeted \
  TARGETS="crates/core/flags/hiargs.rs tests/feature.rs"

Write the three-section packet for another repo to a file:

make bundle-target REPO=/path/to/repo \
  > /tmp/dcck-packet.md

Print just the LLM handoff section for the current repo:

make handoff

Run a targeted change-risk pass for specific files while staying inside the cloned repo:

make risk-target TARGETS="README.md scripts/change_risk.sh"

make risk-target is repo-local. It scopes the change-risk output to files inside the current cloned DCCK repo; for another repo, use make bundle-target REPO=/path/to/repo TARGETS="..." instead.

Output Shape

The bundle emits three markdown sections to stdout in this order:

1. # Project Map
2. # LLM Handoff
3. # Change Risk

Reference section shapes live in templates/.

Example Packet

• examples/control-sample-packet.md is a redacted sample captured from the venture control run.
• It shows the emitted section order and tone without leaking the full workspace path.

Templates

• templates/project-map.md
• templates/llm-handoff.md
• templates/change-risk.md

These are fixed reference layouts for the v0 bundle. They are not runtime inputs yet; they define the intended shape so the packet can be used without opening archive notes first.

Current Scope

• Local-only
• Shell-first
• No accounts
• No spend
• No hosted service

Release Notes

• LICENSE ships the planned MIT terms for the first public repo shape.
• REPO-CHECKLIST.md is the publish-safe preflight list for the first SPA-001 GitHub push.
• make handoff exposes the middle LLM-oriented section directly so the public repo has the same one-command affordance as bundle, map, and risk.
• make bundle-target REPO=/path/to/repo [TARGETS="..."] exposes the outside-repo packet flow behind the same repo-local make affordance as the rest of the kit.
• make check now runs against the repo-local fixture repos under fixtures/, so the regression guardrail no longer depends on Jane-local /tmp clones or the venture workspace path.

---

More free tools by HumanKaylee

• Prompt Starter Pack — 20 free battle-tested prompt templates for code review, debugging, and architecture decisions, plus a 40-template Premium Pack ($9).
• cron-doctor — AI-powered cron expression generator + silent cron-job failure detector.
• ai-context-gen — generates IMPLEMENTATION_NOTES.md context files so AI coding assistants understand your codebase in one shot.