agentleFS
Sign inStart free
cedaniel200cedaniel200/atlas-template/.agents/skills/update-harness/SKILL.md

update-harness

Skill3 starsChanged 22 days agoMITView on GitHub

Use when the user asks to update the template or the harness (any language: "update the template", "actualiza el arnés", "mettre à jour le template", "template aktualisieren"). Applies ownership rules, resolves conflicts and updates the manifest/state.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Not mid-change: finish or archive first.

    line 14
  2. Very specific:

    Do not improvise hashes: use sha256.sh/sha256.ps1 or the scripts.

    line 34
  3. Distinctive:

    If the template removes a file, report it.

    line 36

≈ “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 the harness

Flow to bring a new template version into a configured project. It never overwrites owned files and never deletes files.

When

  • The user asks to update the template/harness, or a new tag/commit exists.
  • Not mid-change: finish or archive first.
  • Trigger phrases may arrive in any language — match the intent ("actualiza el arnés", "update the template", "mettre à jour", "aktualisieren"), not the exact wording.

Steps

  1. Check state: .atlas/state.json (template_source) and .atlas/manifest.json.
  2. Get the new template in a temp directory (git clone + checkout <tag|commit>).
  3. Run the script from the project root: node .atlas/scripts/actualizar-arnes.mjs --template <path>
    • owned → skipped · generated → regenerated (adapters with resolved placeholders) · managed → replaced if the hash matches, otherwise <file>.new.
    • It backs up and rewrites manifest.json and state.json (version, commit, hashes).
  4. Resolve conflicts: diff -u <file> <file>.new, merge by hand and remove the .new.
  5. Validate: validar-manifiesto, validar-contrato, validar-perfiles, openspec doctor and openspec context.
  6. Commit: chore(harness): update to <version> and report updated/conflicts/skipped.

Rules

  • Do not improvise hashes: use sha256.sh/sha256.ps1 or the scripts.
  • Do not overwrite owned (AGENTS.md, config, docs, adr, specs).
  • If the template removes a file, report it; do not delete it.
  • Packs are enabled/disabled by hand (.atlas/packs/README.md).

Human guide: docs/harness/es/UPDATE.md (or docs/harness/en/UPDATE.md).

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