Replace the ~31-command self-review chain triplicated in CLAUDE.md, AGENTS.md and CONTRIBUTING.md with `tools/gauntlet.sh` — deferred until a decision row approves it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation, tooling
Research direction
Start with the gauntlet blocks between the markers in CLAUDE.md, AGENTS.md and CONTRIBUTING.md, then the comparison in tests/test_guard_wiring.py. The issue says a decision row in docs/roadmap/risks-and-decisions.md must approve the change before any work begins. Done means tools/gauntlet.sh exists, the three documents and the meta-test call it, and the doc-versus-doc comparison is removed.
Written by the indexing model from the issue text.
Description
Deferred work ·
S1-addendum: tools/gauntlet.sh· severity Low · cost ~2-4 h · recorded indocs/roadmap/risks-and-decisions.md:250
Summary
The gauntlet is copied three times, and tests/test_guard_wiring.py exists partly to keep the copies identical and to catch a trailing || true that would bind to the whole && chain. The S1 addendum called a single tools/gauntlet.sh genuinely attractive — it deletes the doc-versus-doc half of the meta-test and makes the || true precedence hazard structurally unreachable — but deferred it because it changes the contributor-facing procedure while Phase 16 steps were still landing.
Condition or budget
Its own decision row in risks-and-decisions.md first; proposed for Phase 16 S14 (#900) or S16 (#902).
State today (re-checked 2026-10-09)
No tools/gauntlet.sh exists; the chain is triplicated between the gauntlet markers of the three documents.
Related
#703 (the gauntlet is not the full CI pull-request surface) and #717 (|| true wording).
Acceptance criteria
- A decision row records the change; the three documents and the meta-test call the script, and the doc-versus-doc comparison is retired.
Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09.
- Dominant language
- Python
- Stars
- 9
- Forks
- 1
- Avg merge
- 11h 6m
- Merged PRs (30d)
- 29
Getting set up
- Ships a 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 HodeTech/ForgeLM
-
area: site bug good first issue severity: low wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
HodeTech/ForgeLM#961 · 1 comment ·
Maintainers usually reply within 1 day
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
documentation severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in HodeTech/ForgeLM
Similar issues
-
comp/cli P3 type/security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NousResearch/hermes-agent#141420 · 1 comment ·
Maintainers usually reply within 1 day
-
vendor-pitch
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
bug llm p2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
New tool: ZIPZAX Python Notebook StudioPossibly taken @github-actions claimed this today. Opensubmission triage
Difficulty 1/5 Under an hour Newbie friendliness 68/100
kausalflow/tools#226 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100