bug-tracker-render

Regenerates the repo-wide bugs-tracker.html from bug folders using a Python script.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill bug-tracker-render-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-tracker-render
Source: https://github.com/cagriy/dev-skills/tree/main/skills/bug-tracker-render
Command: npx skills add https://github.com/cagriy/dev-skills --skill bug-tracker-render-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping a human-readable HTML bug tracker in sync with the actual bug reports on disk is error-prone when done by hand. This Skill rebuilds the tracker wholesale from the filesystem so it can never drift from reality. ## Core Features & Use Cases - Wholesale tracker regeneration: Runs scripts/render_bug_tracker.py to scan bugs/ (open) and bugs/archive/ (closed) and rewrite bugs/bugs-tracker.html from a template. - Derived status, no stored state: Open versus closed is always re-derived from folder location, so create and update are the same operation. - Graceful degradation: Missing script, template, or git work tree produces a single skip line rather than an error that aborts the calling skill. - Use Case: After bug-submit files a new report or bug-fix closes one, this helper is invoked as a sub-step to refresh the tracker page with expandable issue cards and relative-path screenshots. ## Quick Start Ask the bug-submit or bug-fix skill to file or close a bug, and it will invoke this helper to regenerate the bugs tracker page automatically.

Frequently Asked Questions about bug-tracker-render

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

FAQPage Schema
How do I regenerate the bugs-tracker.html file?

Run the render_bug_tracker.py script with python3; it scans bugs/ for open issues and bugs/archive/ for closed ones, then rewrites bugs/bugs-tracker.html from its template. This skill is normally invoked automatically by bug-submit or bug-fix.

Can I invoke bug-tracker-render directly as a user?

No, it is marked user-invocable: false and runs only as a sub-step of other skills in the plugin, specifically bug-submit Step 8 and bug-fix Step 9c, whenever the set of bugs on disk changes.

Does the bug tracker store open or closed status anywhere?

No, status is derived, never stored. A folder in bugs/ means open and a folder in bugs/archive/ means closed, so the tracker is rebuilt wholesale from the filesystem on every run and cannot drift from reality.

What happens if the render script or template is missing?

The skill outputs a single skip line such as "bug-tracker-render: skipped — script not found" and stops. A skip is a note, not an error, so the calling skill continues and no hand-written tracker is substituted.

Does the tracker script need any Python packages installed?

No, the script is stdlib-only and runs with the system python3 interpreter rather than a project environment. It locates the repo root by walking up from the current directory and uses the template shipped next to it.