Add the forge-groom skill #51
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/memory!51
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/forge-groom-skill"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds the
forge-groomskill: the behavioural contract for a weekly tracker triage that any harness can run by hand and a timer will run unattended, plus its index entries in the README.Nothing changes for a running machine; this is memory prose, and no timer exists yet.
The skill's action table is the whole autonomy boundary: close only on a merged
Closes, set five named labels, write one plain-text report; everything else is forbidden, andRefsis reported rather than closed on because memory reserves it for non-final PRs.Also retires the
flake-status --upstreamgotcha inallod.md, which described the bug fixed by allod/tools#177, replacing it with the current behaviour.What proves it: the plan's slice 1 witness is a by-hand run of this skill over allod/tools reproducing the 2026-09-09 manual pass; that run happens after this merges.
If it is wrong, revert; nothing reads the skill yet.
Refs allod/strategy#48
The plan that schedules the rest (the
forge pr list -sflag in tools, the archetypes timer and msmtp module, the private enablement) isallod/strategydev-plans/forge-groom.md, opened alongside this PR.Risk
R1. Prose only. The one behavioural risk is a future runner misreading the action table; the table is positive and enumerable for that reason, and the timer will additionally hold a token that cannot push or merge.
Validation
nameanddescriptionin the Agent Skills format thatfleet-diffuses.allod.mdline forflake-statusmatches the merged behaviour in allod/tools#177.