πΏ 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>| Type | When to use |
|---|---|
feat | New content (chapter, lexicon entry, new section) |
fix | Corrections (broken links, wrong facts, typos) |
chore | Maintenance, refresh, backlog, agent-only files |
docs | Meta files only (rules, skills, plans) |
Examples:
feat/owasp-2025-alignmentchore/vault-refresh-2026-06fix/broken-links-auditchore/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-rununder.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-workbranch 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.