ericpardee Deliverable Check
Deliverables must read as standalone artifacts written by a fresh author. This skill makes that rule mechanical instead of remembered.
Usage
python3 ~/.claude/skills/deliverable-check/scripts/lint.py <file> [<file> ...]
Exit 0 clean, 1 findings (printed as file:line: [rule] text), 2 read error.
Workflow
- Run the linter on the deliverable file(s).
- Fix every finding by rewriting the sentence as if no prior version ever existed. Do not delete content the reader needs; restate it standalone.
- Re-run until clean.
- Only then present, post, or send the deliverable.
What it catches
- Metaspeak: "as discussed", "per your feedback", "updated to reflect", "previous draft", "I've revised", "now includes", and similar references to drafts, revisions, reviewers, or process.
- Em and en dashes (house style bans them).
- The "isn't just X, it's Y" trope.
Limits
The regex list is a floor, not a ceiling. After a clean lint, do one human-eye
pass for subtler process references the patterns cannot catch (for example a
paragraph that only makes sense if the reader saw an earlier version). Add any
new offender you meet to scripts/lint.py in the same turn.