Skip to content

🌿 Branches, PRs & Notifications

Git is the natural guardrail for a custodian agent. It turns a risky action (β€œthe agent modifies the vault”) into a reversible proposal (β€œthe agent opens a branch with a diff”).

Branch convention

Recommended format β€” aligned with .agents/rules/git-workflow.md:

<type>/<short-objective>
TypeWhen to use
featNew content (chapter, lexicon entry, new section)
fixCorrections (broken links, wrong facts, typos)
choreMaintenance, refresh, backlog, agent-only files
docsMeta files only (rules, skills, plans)

Examples:

  • feat/owasp-2025-alignment
  • chore/vault-refresh-2026-06
  • fix/broken-links-audit
  • chore/lexique-backlog-cleanup

Minimum content of an agent PR

A PR generated by an agent should include:

  • readable summary;
  • modified files;
  • external sources consulted;
  • commands executed;
  • limits and assumptions;
  • human review checklist.

Notifications

Possible channels:

  • GitHub PR;
  • email;
  • Slack/Matrix/Discord webhook;
  • run log file via vault-log-run under .agents/vault-maintenance/runs/ (primary audit trail for non-interactive runners or tasks with no PR).

The channel matters less than the rule: notification does not equal validation.

Anti-patterns

  • single agent-work branch reused indefinitely;
  • direct commit to main;
  • PR without sources;
  • notification that automatically triggers merge;
  • agent that reruns a superseded task because an old plan still has TODOs.

See also

Give my opinion

Everything is optional: one answer is enough. This site sends nothing: you send it, the way you choose.

Your noteNo note
Your opinion is about
About what? (several choices possible)
What will be sent
Send by e-mail

Private, no account: opens your mail program with the message ready, for ia-on-prem@damien.becherini.fr.

Open a GitHub issue β†—

Public, with a GitHub account. You read the issue again before you publish it.

To paste it wherever you want.

Give at least a note, a subject or a message to be able to send.