agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/.agents/skills/git-actualizar/SKILL.md

git-actualizar

Skill4 starsChanged 4 days agoMITView on GitHub

[Rutina] Sincronizar proyecto (origin) y comprobar novedades del framework DT (upstream). No toca session.yaml. Use when the user invokes /actualizar.

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Dos fases independientes: No crea, no resetea ni modifica vitals/ops/session.yaml.

    line 8
  2. Very specific:

    No ejecutar apply de sync desde /actualizar.

    line 46
  3. Distinctive:

    No invocar scripts Ruby para Fase B.

    line 47

≈ “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.

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

git-actualizar

Dos fases independientes. No crea, no resetea ni modifica vitals/ops/session.yaml.

Instrucciones upstream (Markdown): references/upstream-check.md · spec vitals/specs/dt-upstream-config.md.

Fase A — Proyecto (siempre)

  1. Resolver git_root (si existe vitals/workspace.yaml, respetar multi-proyecto).
  2. Ejecutar:

    git fetch origin
    git pull --rebase
  3. Reportar breve: commits traídos o "al día", rama actual, conflictos si los hay.

Fase B — Framework DT (consulta only)

Seguir todo references/upstream-check.md.

Resumen: leer vitals/config/dt-upstream.md, comparar semver con tags de dt-upstream, avisar si hay release nueva → ofrecer /actualizar-dt. No checkout. No scripts Ruby.

Post-Fase A (opcional)

Tras pull grande en rules/commands/skills del proyecto, sugerir /setup o post-sync-pipeline.md.

Sesión

Si no existe vitals/ops/session.yaml or operator.id vacío → una línea: "Para trabajar con identidad en este repo, usá /yo."

Conflictos (Fase A)

  • Listar archivos en conflicto; no push --force en main/master.
  • Tras resolver: /guardar si va a commitear.

No hacer

  • No tocar vitals/ops/session.yaml.
  • No ejecutar apply de sync desde /actualizar.
  • No invocar scripts Ruby para Fase B.

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.