.github/DEAD-FILE-AUDIT.md says "60 generated explainer pages"; there are now 61
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
The issue points to a specific file, .github/DEAD-FILE-AUDIT.md, and a specific line about '60 generated explainer pages'. First, verify the current count of explainer files by running the provided commands (ls explainers/*.md | wc -l). Then, edit the audit file to update the number to 61 or rephrase the sentence to avoid a hardcoded count. Finally, ensure no other references to the count need updating by checking the script scripts/check_explainer_count.py.
Written by the indexing model from the issue text.
Description
Where: .github/DEAD-FILE-AUDIT.md, the explainers-ui.js bullet under the assets/ section.
The gap: The audit doc states: "explainers-ui.js - referenced only by index.html... None of the 60 generated explainer pages load it..." - but explainers/*.md (and the generated explainers/*.html pages) currently number 61, not 60:
$ ls explainers/*.md | wc -l
61
$ python3 scripts/check_explainer_count.py
OK: all 6 explainer-count mentions match explainers/*.md (61 files).
$ git log -1 --format='%h %ci' -- .github/DEAD-FILE-AUDIT.md
501932d 2026-09-10 01:43:03 +0530
The doc was last touched Sep 10; at least one explainer has been added since, so its hardcoded count drifted the same way scripts/check_explainer_count.py exists specifically to catch elsewhere (README.md, CONTRIBUTORS.md, METRICS.md, ROADMAP.md) - this file just isn't on that script's watch list.
Fix direction: Either update "60" to the current count, or reword to avoid a point-in-time number (e.g. "none of the generated explainer pages load it").
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 1h 53m
- Merged PRs (30d)
- 97
Getting set up
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 yakew7/Fair-Code
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
yakew7/Fair-Code#731 · 1 comment ·
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#611 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
isocpp/CppCoreGuidelines#2338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
polka-codes/test#345 ·
Maintainers usually reply within 1 day