check-open-questions.sh grades clean when register rows sit under a sub-heading
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start by reading plugins/planning/scripts/check-open-questions.sh, especially extract_section and the ledger parsing that counts register rows. Reproduce with a ledger containing Q1-Q2 in the register and Q3 under ### Round 2, then run check-open-questions.sh --ledger <file>. Done when the gate either counts every Q row or exits 2 and names rows outside the register section.
Written by the indexing model from the issue text.
Description
Problem
plugins/planning/scripts/check-open-questions.sh (planning 0.76.0) reports status=clean when register rows sit below a sub-heading inside ## Open-question register. Any heading ends the section (extract_section: /^#+[[:space:]]/ { exit }), so rows after a ### Round 5 heading are never read, and the gate grades only the rows above it.
Observed 2026-10-18 on a re-interview ledger that appended rounds under ## Round N and then ### Round N headings: registered=35 open=0 … status=clean procedure=ok, while 27 more rows (Q36-Q62) were below the headings. With the headings removed: registered=62. Had any of those 27 rows been open, the gate would still have reported clean.
The skill tells re-interviews to append ## Resolved (<round>, <date>) sections to the ledger, which invites headings near the register.
Expected
Either the gate reads every - Q<N> | row in the ledger, or it fails (exit 2, ungradeable) when a - Q<N> | row exists outside the register section, naming the line.
Repro
- A ledger with
## Open-question register, rows Q1-Q2, then### Round 2, then- Q3 | open | round 2 | x? |. - Run
check-open-questions.sh --ledger <file>. - It prints
registered=2 open=0 … status=clean.
🤖 Generated with Claude Code
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 8h 44m
- Merged PRs (30d)
- 926
Getting set up
- No Dockerfile or Docker Compose file
- No 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 melodic-software/claude-code-plugins
-
status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
melodic-software/claude-code-plugins#8537 ·
Maintainers usually reply within 1 day
-
priority: medium status: confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#8507 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
melodic-software/claude-code-plugins#8476 · 1 comment ·
Maintainers usually reply within 1 day
-
area: security needs-human priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#8472 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#8434 · 1 comment ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
uno-testing: the step-by-step procedure serializes tool use (1.7 vs 2.3 tools/call)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
unoplatform/studio#200 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
phusion/passenger-docker#480 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
quickemu-project/quickemu#1963 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
source:reader type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
stephrobert/blog-roadmap#95 ·