IMPLEMENTAUDIT
On this page
  1. Rule
  2. Run-root exclusion
  3. Audit use
  4. Source surfaces
  5. Why one-revision diff matters
  6. Helper modes
  7. Review pattern
Evidence

Repo state comparison

How deliverable changes are separated from run evidence files.

Run evidence is not the product diff.

The work record explains the run, and phased work may add a run folder.
Final audit still needs to separate product files from audit files, so .IMPLEMENTAUDIT/ evidence does not masquerade as deliverable output.

Rule

Repo-state evidence records committed, staged, unstaged, deleted, and untracked changes against a baseline.

Run-root exclusion

Evidence files under .IMPLEMENTAUDIT/ are excluded from deliverable proof so the run folder does not masquerade as product output.

Audit use

The final audit can compare what changed in the repo against the planned deliverables, then separately cite run evidence.

Source surfaces

skills/implementaudit/references/repo-state-comparison.md and the shipped helper ${IMPLEMENTAUDIT_SKILL_DIR:-skills/implementaudit}/scripts/repo-state.sh.
In a source checkout, the skills/implementaudit fallback resolves helper scripts. In an installed package, first export IMPLEMENTAUDIT_SKILL_DIR to the loaded skill directory containing SKILL.md, scripts/, references/, and templates/.
Do not point IMPLEMENTAUDIT_SKILL_DIR at the repo root, the IMPLEMENTAUDIT.skill archive file, or IMPLEMENTAUDIT_BASE; IMPLEMENTAUDIT_BASE is the run-root base when used.

Why one-revision diff matters

git diff <baseline> compares the baseline commit to the current working tree, including staged, unstaged, deleted, and committed-after-baseline changes.
A commit range can miss uncommitted work.
Untracked files are listed separately with git ls-files --others --exclude-standard; ignored files need an explicit override.
If the baseline is invalid, the evidence degrades to existence-only instead of pretending the comparison succeeded.

Helper modes

ModeUse
deliverableCheck whether a path is present, missing, untracked, changed, unchanged, or baseline-unavailable.
changed-filesFeed final audit and release-readiness review.
added-linesFeed cleanliness and overclaim scans; includes untracked text files.

Review pattern

Use the work record, and the run folder when present, to explain the audit.
Use repo-state comparison to answer what the product diff actually changed.
A valid final audit can cite both, but it should not count audit files under .IMPLEMENTAUDIT/ as product deliverables.

Repo-state helpersreview
$ export IMPLEMENTAUDIT_SKILL_DIR="$HOME/.codex/skills/implementaudit"
$ bash "${IMPLEMENTAUDIT_SKILL_DIR:-skills/implementaudit}"/scripts/repo-state.sh changed-files <baseline>
$ bash "${IMPLEMENTAUDIT_SKILL_DIR:-skills/implementaudit}"/scripts/repo-state.sh deliverable <baseline> src/app.txt
$ bash "${IMPLEMENTAUDIT_SKILL_DIR:-skills/implementaudit}"/scripts/repo-state.sh added-lines <baseline>