Individual skill
milestone-sweep
Runs verify, triage, next-milestone, fix and release-gate across every philoserf repo, one background agent per repo in its own worktree, and stops before shipping. Use when asked to sweep, groom or get the philoserf repos release-ready. Holds every decision for one batch at the end.
skills/milestone-sweep/SKILL.md
Source commit 83315e4f8206fad56f9791a8f7884eec5609296a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- dotfiles Repository topic
- hooks Repository topic
- agent-skills Repository topic
- claude-code-config Repository topic
- claude-skills Repository topic
- code-review Repository topic
- release-automation Repository topic
- subagents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Milestone sweep
One agent per repo under `~/source/philoserf/`, each working its repo end to end in a linked
worktree: verify, triage, pick the next milestone, ship it with `issue-pr`, gate it with
`release-gate`, stop before tagging. You orchestrate and do not touch the repos yourself
while their agents run.
**Run it on `almanac`, from a session started in `~/source/philoserf`.** `almanac` is the
always-on host. Twenty agents report back over an hour or more, and nothing here needs
`sextant`. Starting anywhere else, such as `~/notes`, roots the language server outside the
repos. It then sends a stream of false "module not in workspace" and `undefined:` errors
about files that compile.
## 1. Sync, then list the repos