Skip to content

DanRedelien/codebase-optimization-kit

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

codebase-optimization-kit

codebase-optimization-kit is a disposable, JSON-first agent-ops runtime for large codebase optimization passes.

The primary artifact is the installed folder:

.codebase-optimization-kit/

Copy that folder into a target project, then tell the coding agent to read:

.codebase-optimization-kit/AGENT.md

The kit helps agents build a project census, suggest zones, plan multi-agent discovery, record evidence-backed findings, create implementation packets, and enforce packet scope before completion.

It is not a permanent project dependency, documentation system, MCP server, autonomous refactoring engine, or LOC reduction bot. Delete it after the optimization pass once final reports are exported and accepted work is merged or abandoned.

Runtime Layout

templates/optimization-kit/
  AGENT.md
  SAFE_TO_DELETE.md
  kit.py
  kit_runtime/
  schema/
  state/
  policies/
  templates/

When installed, this becomes:

project/
  .codebase-optimization-kit/

JSON and JSONL files under state/ are the source of truth. Only state/project.json ships by default; doctor creates the remaining state files on first run. Markdown files are short entrypoints, editable policy templates, or generated reports.

Manual Copy Workflow

Manual copy is the first-class workflow:

cp -R templates/optimization-kit /path/to/project/.codebase-optimization-kit

Then, in the target project:

python .codebase-optimization-kit/kit.py doctor
python .codebase-optimization-kit/kit.py census
python .codebase-optimization-kit/kit.py zones suggest
python .codebase-optimization-kit/kit.py agents plan
python .codebase-optimization-kit/kit.py agents prompts

Optional Installer

The optional safe copier preserves existing project and kit state files:

python scripts/init.py /path/to/project

Useful flags:

Flag Meaning
--dry-run Print planned actions without writing files.
--target-dir .codebase-optimization-kit Use a custom relative target directory.
--overwrite-kit-files Refresh kit-owned runtime files only. State, findings, packets, reports, locks, and decisions are preserved.

Installer safety rules:

  • It never deletes project files.
  • It never writes or overwrites root AGENTS.md.
  • It never overwrites existing project files.
  • It preserves existing kit state, findings, packets, reports, locks, and decisions.
  • In git projects, it writes the managed ignore block to .git/info/exclude; outside git it falls back to .gitignore.
  • It refuses symlink or junction installs.

Runtime Commands

python .codebase-optimization-kit/kit.py doctor
python .codebase-optimization-kit/kit.py census
python .codebase-optimization-kit/kit.py zones suggest
python .codebase-optimization-kit/kit.py agents plan
python .codebase-optimization-kit/kit.py agents prompts
python .codebase-optimization-kit/kit.py findings add --file finding.json
python .codebase-optimization-kit/kit.py findings validate
python .codebase-optimization-kit/kit.py reconcile
python .codebase-optimization-kit/kit.py packets create --finding DEAD-001
python .codebase-optimization-kit/kit.py packets validate
python .codebase-optimization-kit/kit.py validate
python .codebase-optimization-kit/kit.py validate --enforce-packet
python .codebase-optimization-kit/kit.py report
python .codebase-optimization-kit/kit.py contracts candidates
python .codebase-optimization-kit/kit.py locks acquire --scope Z-core
python .codebase-optimization-kit/kit.py locks release --scope Z-core
python .codebase-optimization-kit/kit.py status

Core runtime behavior uses Python 3.10+ and the standard library. It may detect existing project tools, but baseline census, zones, planning, validation, and reporting do not require package installation.

Audit criteria live in .codebase-optimization-kit/policies/audit-criteria.json; enforced audit helpers live in kit_runtime/audit.py. Generated agent tasks include a compact audit_queue of lanes, and findings must use known categories or project-local custom_finding_categories.

agents prompts does not launch agents. It materializes copy-paste discovery prompts from state/agent-tasks.jsonl into the single managed directory state/agent-prompts/. Tag state/agent-prompts/TASK-XXX.md in a clean agent chat to run one planned task, and keep task-local findings in state/task-findings/TASK-XXX.jsonl until a coordinator merges or validates them.

Validation

Validate an installed runtime through the wrapper:

python scripts/validate.py /path/to/project

The wrapper delegates to:

python .codebase-optimization-kit/kit.py doctor
python .codebase-optimization-kit/kit.py validate

Use --enforce-packet to fail when changed project files are outside the active approved packet.

Core Rules

  • Project docs, tests, and public contracts remain the source of truth.
  • Discovery agents do not modify project source.
  • Findings must be structured JSON/JSONL records.
  • Implementation requires an approved packet.
  • Implementation agents may edit only packet-listed files.
  • Risk 4 packets require explicit human approval.
  • Risk 5 work cannot be implemented directly from the kit.
  • Dead-code deletion and behavioral parity require structured evidence.
  • Audit findings require lane-specific evidence; security risk is risk 5 and blocked from direct kit implementation.
  • security-risk is queued only for security-sensitive path signals; normal source/config zones use lower-consequence audit lanes first.
  • Reports are generated views over JSON state, not source of truth.

Maintainer Docs

Maintainer notes live under docs/ and are not installed into target projects.