refresh-status

Regenerates STATUS.md from committed benchmark reports, CI pipelines, plan docs, and README claims.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/polycode-public/the-mechanical-code-talker --skill refresh-status-polycode-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refresh-status
Source: https://github.com/polycode-public/the-mechanical-code-talker/tree/main/.claude/skills/refresh-status
Command: npx skills add https://github.com/polycode-public/the-mechanical-code-talker --skill refresh-status-polycode-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a repository's STATUS.md capability summary accurate is tedious: benchmark reports, CI pipeline results, design plan statuses, and README claims all drift out of sync, and manually re-auditing them is error-prone. This skill resynthesizes STATUS.md from already-committed sources without running benchmarks or editing source docs. ## Core Features & Use Cases - Benchmark summary synthesis: Enumerates reports/BENCHMARK_.md files, prefers summary reports, cites every row's source file, and stamps the measured-tree version honestly. - CI pipeline reporting: Fetches the latest finished pipeline on main via glab, maps every job to the consumer surface it exercises, and reports real pass counts, wall-clock time, and failures. - Plan and README audit: Classifies each PLAN_.md remainder into design-horizon vs research-horizon buckets and cross-checks README capability claims against shipped, tested code in both directions. - Use Case: After a new benchmark sweep lands and a pipeline resolves on main, invoke the skill to regenerate STATUS.md with cited sources, an honest measured-tree banner, and a list of README omissions to fix separately. ## Quick Start Tell the session to follow the refresh-status skill to regenerate STATUS.md from the committed reports and latest CI run.

Frequently Asked Questions about refresh-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I regenerate STATUS.md from benchmark reports?▼

Invoke the refresh-status skill, which enumerates committed reports/BENCHMARK_*.md files, prefers any summary report, cites each row's source file, and rewrites STATUS.md at the repo root. It never runs benchmarks itself or edits the source reports.

How do I summarize the latest GitLab CI pipeline in documentation?▼

The skill fetches the most recent finished pipeline on main using glab ci status and the pipelines jobs API with per_page=100. It maps every job to the consumer surface it tests and reports real job counts, wall-clock time, and any failures.

Does this skill run benchmarks or trigger CI pipelines?▼

No. It only reads already-committed benchmark reports and the latest pipeline that already ran. If an axis has no report, STATUS.md says not yet measured rather than inventing numbers.

How does the skill audit README claims against actual code?▼

It walks every README section, extracts the headline capability claim, and checks three columns: implementing module, consumer surface, and named test tier. It also greps for shipped pages and shipped plan slices missing from README to find under-selling omissions.

When should I not use the refresh-status skill?▼

Do not use it to fix stale README content, run new benchmark sweeps, or edit plan docs; those are separate reviewable changes. It only resynthesizes STATUS.md from existing committed sources and reports findings.