From git-workflow-guards
Run all repo-health garbage-collection scans in parallel. Dispatches each `gc-*` subvariant in its own sub-agent so the scans run isolated and without polluting each other's context, then reports a per-scan summary count. Use when running a manual repo-health pass; subvariants currently include `gc-stale-todos` and `gc-duplicated-blocks`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-workflow-guards:gc-runThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the orchestrator for this repo's garbage-collection scans. Your single job is to dispatch each `gc-*` subvariant as its own sub-agent, in parallel, and then report a one-line summary per subvariant. You do not perform the scans yourself — the sub-agents do.
You are the orchestrator for this repo's garbage-collection scans. Your single job is to dispatch each gc-* subvariant as its own sub-agent, in parallel, and then report a one-line summary per subvariant. You do not perform the scans yourself — the sub-agents do.
Run on a manual cadence (cron-eligible, weekly is sensible). Not human-invoked at action boundaries.
Currently shipped:
gc-stale-todos — finds TODO/FIXME/XXX/HACK comments where git blame shows the introducing commit is more than 30 days old.gc-duplicated-blocks — finds blocks of more than 30 lines duplicated across the repo with at least 80% similarity.If a future subvariant is added to this plugin (named gc-<something>/SKILL.md), the orchestrator picks it up automatically.
git status --porcelain
If there are uncommitted changes, stop and tell the user to commit or stash first. There is no --force override — the scans must run against a clean checkout because uncommitted edits skew git blame ages and leave noise in the duplicated-blocks survey.
Spawn one sub-agent per subvariant by issuing multiple Task tool invocations in a single assistant message (not back-to-back across turns — that's sequential, not parallel). Each sub-agent runs the matching skill end-to-end and is responsible for its own filing, summary, and stop conditions.
Brief each sub-agent with:
gc-stale-todos skill end-to-end against this repo")..beads/, gh auth, etc.) — otherwise let the sub-agent detect.Do not brief the sub-agent with extra heuristics or "be careful about X" — the skill files already encode their own discipline. Wrapping them in extra prose dilutes the contract.
When all sub-agents finish, print one line per subvariant in this shape:
=== gc-run summary ===
gc-stale-todos: filed N issues, skipped M candidates
gc-duplicated-blocks: filed N issues, skipped M candidates
If a sub-agent fell back to a markdown report (no tracker wired up), substitute the report path for the issue count: gc-stale-todos: wrote gc-findings/stale-todos-<date>.md.
If a sub-agent failed (errored out, hit a permission prompt, exhausted its token budget, timed out, or got stuck in a loop without returning), print:
gc-<name>: FAILED — <one-line reason>
…and continue to report the others. One scan failing does not block the rest.
The orchestrator's job is dispatch and summary, not re-display. The findings are already in the tracker (or a fallback report file); duplicating them in the orchestrator's output wastes context and tempts the user to act on the orchestrator's transcribed copy instead of the canonical tracker entry.
If the user wants to drill into a specific finding, they go to the tracker.
git status --porcelain shows uncommitted changes, stop and tell the user before dispatching.npx claudepluginhub zainrizvi/git-workflow-guards --plugin git-workflow-guardsProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.