cobol-o-matic: Skill for Claude Code

Cleaning a Workspace

Remove all generated artifacts so the workspace is ready for a fresh run.

What to Clean

There are three categories of generated files. Clean all three for a full reset, or selectively clean specific categories.

1. Output Artifacts

Generated markdown files under the output/ directory (path from config.yaml).

output/
├── business-rules/*.md    # Per-program business rules
├── inventory/*.md         # programs.md, copybooks.md, jcl-jobs.md
├── data/*.md              # data-dictionary.md, file-layouts.md, database-operations.md
├── flows/*.md             # program-call-graph.md, batch-flows.md, data-flows.md
├── integration/*.md       # interfaces.md, io-map.md
└── requirements/*.md      # capabilities.md, modernization-notes.md

Remove all .md files from each subdirectory. Preserve the empty directories.

2. Staging Files

Chunked source files and manifests under the staging/ directory (path from config.yaml, default ./staging).

staging/
├── program-facts.yaml          # Cross-program extracted facts
└── {program-slug}/             # One directory per staged program
    ├── manifest.yaml
    ├── data-division.cbl
    └── chunk-*.cbl

Remove everything under staging/. Preserve the empty staging/ directory.

3. Run State Files

JSON state files under the state/ directory that track convergence across iterations.

state/
├── .cobol-re-state.json                       # Default/single-program state
├── .cobol-re-state-{program}.json             # Per-program state
├── .cobol-re-state-{program}-{chunk}.json     # Per-chunk state
├── .cobol-re-state-phase1.json                # Phased run state
└── .cobol-re-state-phase3.json

Remove everything under state/. State files are dotfiles (.cobol-re-state-*.json), so a bare state/* glob will miss them. Use rm -f state/.cobol-re-state*.json to match them explicitly. Preserve the empty state/ directory.

4. Lingering Agent Processes