progress-dashboard
Role: Engineering Metrics Dashboard Generator
You generate a self-contained, interactive HTML dashboard that visualizes code quality and security improvement progress over time. The dashboard reads JSON summary files produced by the software-evaluation and vulnerability-scan skills.
Phase 1: Data Collection
1.1 Locate JSON Summary Files
Scan for JSON files in:
docs/evaluation/*.json— software evaluation summariesdocs/security-audit/*.json— vulnerability scan summaries
If no JSON files exist, inform the user that they need to run software-evaluation and/or vulnerability-scan first with JSON output enabled.
1.2 Parse & Validate
More from ymd38/dev-skills
spec-doc
>
13vulnerability-scan
>
12software-evaluation
>
9gh-issue-resolver
Implement and verify a fix for a GitHub Issue whose response plan has already been posted as a comment by gh-issue-planner. Creates a feature branch, applies the agreed plan, runs tests, and opens a Pull Request. Use when the user asks to implement/fix/resolve a planned GitHub Issue. Triggers include requests such as Issueを実装して / Issueを修正して / Issueを対応して, implement issue #N, fix issue #N, resolve issue #N, work on issue #N. Prerequisite: an agreed plan comment must exist on the issue (run gh-issue-planner first if not).
6report-to-issues
|
4gh-issue-planner
Fetch a GitHub Issue by ID using the gh CLI, investigate related code, propose a structured response plan (policy, impact scope, implementation steps), and post the agreed plan as a comment on the issue. Implementation/PR creation is out of scope — use gh-issue-resolver for that. Use when the user provides a GitHub Issue ID or asks to investigate/analyze/plan a GitHub Issue. Triggers include issue IDs like #42 or 'issue 42', requests such as Issueを調査して / Issueの対応方針を立てて, analyze issue #N, plan issue #N, investigate issue, look at issue.
1