agentleFS
Sign inStart free
syangasyanga/astack/skills/astack-update/SKILL.md

astack-update

Skill0 starsChanged 53 days agoMITView on GitHub

Update or reinstall astack.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat invocation as authorization to update and reinstall astack without another confirmation.

    line 9
  2. Very specific:

    Run ./install.sh from the updated checkout even when already current.

    line 13
  3. Very specific:

    When the astack manifest, ${XDG_STATE_HOME:-$HOME/.local/state}/astack/manifest.json, lists claude-router under components, update the …

    line 15
  4. Very specific:

    Run python3 scripts/claude_router.py identity --code-only in the updated checkout.

    line 17
  5. Distinctive:

    When any of these differs, leave the router as it is and report the difference.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update astack

Treat invocation as authorization to update and reinstall astack without another confirmation.

Fetch astack's upstream, then fast-forward its main worktree to remote main when possible. Leave unrelated untracked files and directories in place. If local edits, unpublished commits, or conflicting paths prevent the fast-forward, install from a separate clean worktree at remote main. Preserve the existing work and task branches.

Run ./install.sh from the updated checkout even when already current. Preserve installed harness targets unless the user specifies others. For installer conflicts, use the installer's --force option to back up conflicting files and complete the upgrade. Report any backup locations with the result.

When the astack manifest, ${XDG_STATE_HOME:-$HOME/.local/state}/astack/manifest.json, lists claude-router under components, update the router after the harness install succeeds:

  1. Run python3 scripts/claude_router.py identity --code-only in the updated checkout. Compare components/claude-router/accepted.json with it:

    • result is pass.
    • sdk equals the CLIProxyAPI version in components/claude-router/go.mod.
    • code_sha256 and helpers_sha256 equal the printed digests.

    When any of these differs, leave the router as it is and report the difference. Over an activated router, the install's check would fail and switch Claude Code to direct.

  2. Otherwise run ./install.sh --component claude-router < /dev/null, without --force, with a 600-second timeout. An activated router restarts, which ends requests other routed sessions have in flight.
  3. Report any APPEND, SKIP, or RESTART line, the check lines after CHECK, or the astack: line when it exits 1.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free