B-22: `stats --json` in SKILL.md matches the real payload in zero keys
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli, documentation
Research direction
Start with skill/SKILL.md:261-281, then compare its documented stats payload with the output assembled in stats.ts:70-83 and db.ts:593-604. Update the agent-facing contract to reflect the nested payload, actual field names, and epoch-millisecond lastRanAt value. Confirm that the documented shape matches the stats MCP tool and localpress://stats resource responses.
Written by the indexing model from the issue text.
Description
Severity: medium — SKILL.md is the agent-facing contract.
skill/SKILL.md:261-281 documents a flat payload: filesProcessed, operationsSucceeded, operationsFailed,
bytesBefore, bytesAfter, bytesSaved, percentReduction, lastRunAt, breakdown.
Actual output (stats.ts:70-83 + db.ts:593-604) is nested:
{ site, url, stats: { siteName, filesTouched, totalOps, succeeded, failed, skipped, bytesSaved, bytesIn, lastRanAt, byOperation }, overview, formats, recent, history }.
Every documented key except site is wrong; bytesSaved exists but at the wrong depth; percentReduction,
bytesAfter and breakdown don't exist at all, and lastRanAt is epoch ms rather than the documented ISO string.
The stats MCP tool and the localpress://stats resource return the same payload verbatim, so an agent following
SKILL.md reads undefined everywhere.
Extracted from a repo audit performed 2026-07 (the audit doc it came from was proposed via an unmerged docs PR).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 17h 13m
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
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 gfargo/localpress
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gfargo/localpress#270 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 82/100
gfargo/localpress#258 ·
-
bug needs-verification
Difficulty 4/5 3-5 days Newbie friendliness 52/100
gfargo/localpress#342 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
gfargo/localpress#341 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
gfargo/localpress#340 ·
All issues in gfargo/localpress
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100