← Browse

@geoloeg-ist/are-update

A

Incrementally update documentation for changed files

skillclaude

Install

agr install @geoloeg-ist/are-update --target claude

Writes 1 file into .claude/skills/, pinned to git-cf4c5197.

  • .claude/skills/are-update/SKILL.md

Document


name: are-update description: Incrementally update documentation for changed files disable-model-invocation: true

Update documentation for files that changed since last run.

Steps

  1. Read version: Read .claude/ARE-VERSION → store as $VERSION. Show the user: agents-reverse-engineer v$VERSION

  2. Run the update command in the background using run_in_background: true:

    npx agents-reverse-engineer@$VERSION update --backend claude $ARGUMENTS
    
  3. Monitor progress by polling the latest progress log:

    • Wait ~15 seconds (use sleep 15 in Bash), then use Glob to find the latest .agents-reverse-engineer/progress-*.log file, and Read it (use the offset parameter to read only the last ~20 lines for long files)
    • Show the user a brief progress update (e.g. "12/30 files updated, ~5m remaining")
    • Check whether the background task has completed using TaskOutput with block: false
    • Repeat until the background task finishes
    • Important: Keep polling even if no progress log exists yet (the command takes a few seconds to start writing)
  4. On completion, read the full background task output and summarize:

    • Files updated
    • Files unchanged
    • Any orphaned docs cleaned up

Options:

  • --uncommitted: Include staged but uncommitted changes
  • --dry-run: Show what would be updated without writing
  • --eval: Namespace output by backend.model for side-by-side comparison
  • --concurrency N: Control number of parallel AI calls (default: auto)
  • --fail-fast: Stop on first file analysis failure
  • --debug: Show AI prompts and backend details
  • --trace: Enable concurrency tracing to .agents-reverse-engineer/traces/

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-cf4c5197ee3d2026-07-31