agentleFS
gofixpointgofixpoint/amika/.agents/skills/release-commit-sandbox-image/SKILL.md

release-commit-sandbox-image

Skill301 starsChanged 11 days agoApache-2.0View on GitHub

Create a release commit for a sandbox image version bump. Reads the version changes in sandbox-image/versions.env, verifies the generated bundle and its Go mirror are current, builds a changelog of the pinned-version changes, and creates a commit.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 1 is distinctive, and 12 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.

  • 12

    Very specific

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

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

    Create a release commit for a bump of the pinned tool versions in sandbox-image/versions.env.

    line 8
  2. Very specific:

    Run git diff HEAD -- sandbox-image/versions.env (covers staged and unstaged changes).

    line 20
  3. Very specific:

    If there is no change in sandbox-image/versions.env, error out: "No version change found in sandbox-image/versions.env".

    line 30
  4. Very specific:

    If it reports stale output, run python3 sandbox-image/generate.py and tell the user you regenerated.

    line 38
  5. Very specific:

    Run make test-sandbox-image.

    line 40
  6. Very specific:

    Run git status --porcelain and list any modified files outside sandbox-image/ and go/internal/sandbox/sandbox-image/.

    line 48
  7. Very specific:

    Keep the order they appear in versions.env.

    line 59
  8. Very specific:

    If the diff also touched manifest.toml, steps/, assets/, or verify/, summarize those changes in a separate list under an "Other changes:" …

    line 65
  9. Very specific:

    If a single pin changed, use a more specific subject, e.g.

    line 81
  10. Distinctive:

    Only after the user approves the commit message:

    line 90
  11. Very specific:

    Create the commit with the approved message, adding the release trailer via --trailer:

    line 98
  12. Very specific:

    Do NOT include a Co-Authored-By line in the commit message.

    line 114
  13. Very specific:

    After it merges to main, the new image is published by manually running the Build Base Snapshots workflow with amika_ref set to the merge …

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Create Sandbox Image Release Commit

Create a release commit for a bump of the pinned tool versions in sandbox-image/versions.env. This skill extracts every changed pin, verifies the generated artifacts were regenerated, and creates a well-formatted commit covering the source change and all generated files.

The sandbox image has no version tags of its own: the release is this commit. Publishing happens afterwards, out of band (see step 7).

Procedure

Step 1: Extract the version changes

  1. Run git diff HEAD -- sandbox-image/versions.env (covers staged and unstaged changes).
  2. Parse each changed pin from lines like:
    -CLAUDE_CODE_VERSION=2.1.224
    +CLAUDE_CODE_VERSION=2.1.252
    Record NAME, OLD_VERSION, NEW_VERSION for each.
  3. Also note pins that were added (no - line) or removed (no + line); report those separately from bumps.
  4. If there is no change in sandbox-image/versions.env, error out: "No version change found in sandbox-image/versions.env".

Step 2: Verify the generated bundle is current

Generated files are half of the change, and they must land in the same commit.

  1. Run python3 sandbox-image/generate.py --check.
    • If it reports stale output, run python3 sandbox-image/generate.py and tell the user you regenerated.
  2. Run make test-sandbox-image. If it fails, stop and report the failure — do not commit.
  3. Confirm the working tree includes changes under both sandbox-image/generated/ and the Go mirror go/internal/sandbox/sandbox-image/. If versions.env changed but neither did, something is wrong: stop and report it.

Step 3: Check for unrelated changes

Run git status --porcelain and list any modified files outside sandbox-image/ and go/internal/sandbox/sandbox-image/. If there are any, tell the user which ones and confirm before proceeding — this commit should carry only the version bump and its generated output. Never stage untracked junk such as __pycache__/.

Step 4: Build the changelog

  1. Format each bump as - <NAME>: <OLD_VERSION> -> <NEW_VERSION>, using the pin's lowercased, human name (e.g. CLAUDE_CODE_VERSION -> claude-code, PI_WEB_VERSION -> pi-web, UBUNTU_TAG -> ubuntu).
  2. Keep the order they appear in versions.env.
  3. For Amika's own components (AMIKA_VERSION, AMIKALOG_VERSION, AMIKAD_VERSION), the released tags exist in this repo — if git log --oneline <symbol>@v<OLD>..<symbol>@v<NEW> is short and informative, you may add a one-line summary of what that bump brings. Skip it if the log is long or noisy.
  4. If the diff also touched manifest.toml, steps/, assets/, or verify/, summarize those changes in a separate list under an "Other changes:" heading.

Step 5: Review commit message

  1. Draft the commit message using this format:
[release sandbox-image] Bump pinned versions

Update the sandbox image tool pins and regenerate the bundle and its Go mirror.

Version changes:
<changelog entries from step 4>

If a single pin changed, use a more specific subject, e.g. [release sandbox-image] Bump amika to 0.18.0.

  1. Present the full draft commit message to the user using AskUserQuestion and ask them to review it. The user may request edits — apply any changes they ask for and re-present if needed.

Step 6: Create commit

Only after the user approves the commit message:

  1. Stage the source change and every generated file together:

    git add sandbox-image/ go/internal/sandbox/sandbox-image/
  2. Create the commit with the approved message, adding the release trailer via --trailer:

    git commit \
      -m "[release sandbox-image] Bump pinned versions" \
      -m "Update the sandbox image tool pins and regenerate the bundle and its Go mirror.
    
    Version changes:
    <changelog entries from step 4>" \
      --trailer "Release-Component: sandbox-image"

    There is no Release-Version trailer: the sandbox image is not versioned as a unit, so the component trailer stands alone.

Do NOT include a Co-Authored-By line in the commit message.

Step 7: Confirm and report next steps

  1. Display the created commit (hash + full message) so the user can verify.
  2. Remind the user of the follow-up, which this skill does not do:
    • A pull request for this commit should use the same [release sandbox-image] subject prefix; reuse the changelog from step 4 as the PR body.
    • After it merges to main, the new image is published by manually running the Build Base Snapshots workflow with amika_ref set to the merge commit, once per provider.

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.