install · v2.8.0

Install it into your repo

This installer deliberately does not modify your project. ./install.sh stages an immutable release into .astraler/releases/<version> and stops there. The integration is done by an agent running inside your own repo, after it has read your build commands, your agent config, and your real Git state.

I split it into two steps because a copy-over installer always overwrites the wrong file. It cannot tell what belongs to the harness from what belongs to the project and what the owner owns. The cost is that you run one more agent session and read what it intends to do, instead of typing one command and walking away.

Prerequisites

Install

  1. ./check-requirements.sh
  2. ./install.sh /path/to/your-repo
  3. cd /path/to/your-repo
claude "Read .astraler/releases/2.8.0/ADAPT-HARNESS.md completely and execute it."
  4. claude --agent thomas

Four skills for an existing repo

These four skills exist because real repos are rarely clean. bootstrap-glossary pulls domain vocabulary out of the code itself; each term carries the file it was read from and stays marked unreviewed until the owner confirms it. The rule is extract, never invent: a glossary an agent imagined but wrote in a confident voice is more dangerous than no glossary at all.

batch-triage takes an inherited backlog in one pass instead of one ticket at a time. legacy-testing builds a seam into code that offers nothing to test against. untangle is for repos with no module boundaries left to improve, where a clean restructure would arrive as one diff nobody can review.

The shared cost for all four: this is work you finish before the first ticket can run.

  • batch-triage

    Triage an inherited backlog in one pass — many existing issues at once, rather than one new item at a time.

  • bootstrap-glossary

    Seed CONTEXT.md with the domain terms the code already uses, each term carrying the file it was read from and marked unreviewed until the owner confirms it.

  • legacy-testing

    How to get existing untested code under test — characterisation tests that pin current behaviour, and creating a seam before TDD can attach.

  • untangle

    A refactor path for code too tangled for improve-codebase-architecture — where there are no module boundaries to improve, everything imports everything, and a clean restructure would be one enormous unreviewable change.