rebuild-test-image
Skill8 starsChanged 7 months agoApache-2.0View on GitHub
Make the needed changes. Common scenarios: Pinning bats helpers to a specific version (recommended — currently unpinned and cloned from HEAD): Adding a system tool: This builds and tags the image as ghcr.io/joelbarmettleruzh/ultrainit-test:latest locally. Verify all tests pass with the new image before pushing. Commit and push Dockerfile.test to main. The .github/workflows/docker-test-image.yml workflow triggers only when Dockerfile.test changes on main. The workflow pushes to ghcr.io/joelbarmettleruzh/ultrainit-test:latest. No version tag — always :latest. Trigger a test run (push any change) and verify…
- Deletes or force-pushes
- Installs packages
- Commits and pushes
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/workflows/CLAUDE.mdCLAUDE.md
- lib/CLAUDE.mdCLAUDE.md
- prompts/CLAUDE.mdCLAUDE.md
- schemas/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-bats-testSkill
- add-edge-testSkill
- add-gather-agentSkill
- add-integration-testSkill
- add-synthesis-fixtureSkill
- audit-prompt-schema-syncSkill
- bundle-and-verifySkill
- check-ci-locallySkill
- debug-agent-failureSkill
- fixture-syncSkill
- pre-pr-checklistSkill
- release-ultrainitSkill
- run-testsSkill
- tune-synthesis-contextSkill
- validate-generated-artifactSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Verify all tests pass with the new image before pushing.
- Very specific: line 58
Commit and push Dockerfile.test to main.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Before You Start
Dockerfile.test— the test image definition.github/workflows/docker-test-image.yml— fires only onDockerfile.testpath changes on mainMakefile—test-imagetarget.github/workflows/test.yml— pulls the image from GHCR on every CI run
Steps
1. Edit Dockerfile.test
Make the needed changes. Common scenarios:
Pinning bats helpers to a specific version (recommended — currently unpinned and cloned from HEAD):
# Before (broken — HEAD can have breaking changes):
RUN git clone https://github.com/bats-core/bats-support.git
# After (pinned to a specific tag):
RUN git clone --branch v1.11.1 --depth 1 https://github.com/bats-core/bats-support.gitAdding a system tool:
RUN apt-get update && apt-get install -y --no-install-recommends \
your-tool \
&& rm -rf /var/lib/apt/lists/*2. Build locally
make test-imageThis builds and tags the image as ghcr.io/joelbarmettleruzh/ultrainit-test:latest locally.
3. Run the full test suite against the new image
make test-allVerify all tests pass with the new image before pushing.
4. Push to main
Commit and push Dockerfile.test to main. The .github/workflows/docker-test-image.yml workflow triggers only when Dockerfile.test changes on main.
git add Dockerfile.test
git commit -m "chore: pin bats-support to v1.11.1 in test image"
git push origin main5. Monitor the GHCR image rebuild
gh run list --workflow=docker-test-image.yml
gh run watchThe workflow pushes to ghcr.io/joelbarmettleruzh/ultrainit-test:latest. No version tag — always :latest.
6. Verify the next CI run uses the new image
Trigger a test run (push any change) and verify test.yml pulls successfully:
gh run list --workflow=test.ymlVerify
make test-image && make test-allCommon Mistakes
- No concurrency control —
docker-test-image.ymlhas no concurrency group. Two simultaneous pushes to main withDockerfile.testchanges race to push:latest. If this becomes a problem, addconcurrency: { group: docker-build, cancel-in-progress: true }to the workflow. - GHCR image doesn't exist yet on a fresh fork —
test.ymlwill hang or fail on image pull. Runmake test-imageand push first. - Editing
Dockerfile.teston a branch, not main —docker-test-image.ymlonly fires on main. A branch change won't rebuild the GHCR image. Test locally withmake test-imageand verify before merging.
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
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.

