← ClaudeAtlas

stewardlisted

Sweep every repository your agent sessions have touched, found from the agent's own session records and any roots you name, and run the dev loop's housekeeping across all of them at once — fast-forward each base branch, remove what already merged, keep conversation titles in scheme, and report which branches are ready to merge, which pull requests are blocked, and which worktrees a live session still occupies. Built to run unattended on a schedule, so a question a pass would have stopped to ask lands in the report instead. Use when asked to 巡一遍所有项目, 大内总管, 看看哪些分支该合并了, 定时清理本地环境, 扫一下所有 worktree, sweep all my repos, check on every project, what needs merging across my projects, run the housekeeping, keep my local environment clean. Not for syncing or cleaning the one repository you are standing in, for shipping or merging a branch, or for renaming a single conversation.
Misoto22/skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill Misoto22/skills
# Steward Sweep every repository a session has been working in, run the loop's housekeeping in each, and hand back one report of what is waiting on a person. Read [shared/git.md](shared/git.md) first — base resolution, the force-push rule, what "merged" means after a rebase, and § The home worktree. This skill owns three things the skills it delegates to cannot see: **which repositories exist** (each of them works in one), **which worktrees a session still occupies** (git cannot tell), and **the report across all of them**. Everything else it hands off: | Pass | Delegated to | What the steward adds | |---|---|---| | fast-forward the base | `/dev:sync` | runs it in every repository | | merged branches, worktrees, residue | `/dev:cleanup` | the occupancy list — worktrees it must keep | | conversation titles | `/dev:retitle` | unattended runs propose and never write | | landing a branch | nobody | reported as ready, with the command; `/dev:ship` is the person's to run | It never merges, rebases, resolves a conflict, deletes anything cleanup would keep, or renames a title without the two-column table. ## It runs forked `context: fork` in the frontmatter, because a sweep is a long private session whose transcript the caller never needs. Fifteen repositories produce fifteen fetches, a branch ledger per repository, and every sub-skill's own output; measured on one machine, one sweep covered 15 repositories, 121 worktrees and 44 open pull requests, and none of that intermediat