Weekly agent retro: promote, prune and size-limit the .claude rules from the week's run data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading CLAUDE.md and .claude/agents/gitgalaxy-pr-worker.md; the issue describes a weekly gate that gathers run outcomes, send-back reasons, refused tool calls, budget hits, fix loops, scorecards and lessons-inbox entries. Review the .claude/rules, skills and agent briefs when assessing each week's proposed changes. Done means one capped Sonnet worker opens a PR with recurring failures addressed, lessons promoted, duplicates and obsolete rules pruned, size budgets met, and weekly factory numbers compared; every fourth retro includes an instruction audit.
Written by the indexing model from the issue text.
Description
Standing issue for churn's weekly retro (owner 2026-10-18). Each week the gate collects the week's facts with no model (run outcomes, send-back reasons, refused tool calls, budget hits, fix loops, daily scorecards, unticked lessons-inbox entries) and launches one capped Sonnet worker. That worker opens ONE PR, Part of this issue, that:
- turns the top 1-2 recurring failures of the week into a rule or skill change;
- promotes the waiting lessons and prunes: merges duplicates, drops rules the code or tests now enforce, keeps
.claude/agents/gitgalaxy-pr-worker.mdandCLAUDE.mdeach within a fixed size budget; - compares the factory numbers ($/merged PR, fix loops per PR, idle hours) with the previous week in the PR body.
Every 4th retro also audits CLAUDE.md, .claude/rules, skills and agent briefs for outdated or contradictory instructions. This issue stays open; close it only to retire the retro.
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day