メニュー
Render a self-contained light-theme website with three tabs (bugs found, bug videos, reproduction steps) from a bug-recording output directory. Use when the user runs /bug-report or asks to turn recorded bug findings into a report site.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Read the current project's current and prior Claude Code or Codex sessions, extract every prompt, score five effort metrics 0-100 with reasons, estimate average tokens and time per session, and render a self-contained light-theme HTML report. Use when the user runs /effort-map or asks how much effort, thought, bug-fixing, UX tuning, architecture care, or copy-paste slop went into a project.
Find bugs that were encountered and solved in prior Claude Code or Codex sessions for the current project, then generate a self-contained searchable light-theme HTML bug report. Use when the user asks for a bug catalog, solved-problem history, prior-session bug report, recurring failure inventory, or a BUG to Solution report for the current repository.
Analyze a prompt with Edward de Bono's Six Thinking Hats and produce a polished, self-contained HTML report. Use when the user invokes /hats or $hats, requests Six Thinking Hats analysis, wants a decision reviewed from factual, emotional, cautious, optimistic, creative, and process perspectives, or asks for an illustrated HTML decision report.
Reads every Claude Code session in the user's config directory and renders a self-contained light-theme website with a GitHub-style contribution grid, visual metrics, and 5-10 written insights about the user's agent coding habits and what they are building. Use when the user runs /habit-tracker or asks about their coding habits, activity streak, contribution graph, what they have been building, or a recap of their Claude Code usage.
Rewrite poor git commit messages into a clear conventional-commit history. Reads the last N commits with their diffs, proposes a clean conventional message for each by reading what the code actually changed, then opens a light-theme review UI where the user approves all or each message individually before the history is rewritten. Use when the user runs /fix-git-history or asks to clean up, rewrite, normalize, or fix commit messages or git history into a conventional-commit format.
Audits a running web page for WCAG accessibility issues, captures a screenshot and annotates it with a numbered box over every problem, then renders a self-contained light-theme website with the score, the annotated screenshot, and a fix for each finding. Use when the user runs /accessibility-auditor or asks to audit, check, or report a site's accessibility, WCAG compliance, alt text, color contrast, labels, or screen-reader support.
| name | bug-report |
| description | Render a self-contained light-theme website with three tabs (bugs found, bug videos, reproduction steps) from a bug-recording output directory. Use when the user runs /bug-report or asks to turn recorded bug findings into a report site. |
Turn a /bug-recording output directory into a static report site.
/bug-recording output that holds findings.json,
videos/, and screenshots/). Default: ./bug-recording-output.<findings>/../bug-report-site.findings.json must exist in the findings directory. If it does not, run
/bug-recording first and stop loudly.node report.mjs <findings-dir> [site-dir] [--serve] [--port=7800]
The script reads findings.json, copies each .mp4 and screenshot into the
site's assets/, and writes index.html. With --serve it then serves the
site over HTTP (with byte-range support so videos seek) and prints the URL.
A single self-contained HTML file (inline CSS and JS, light theme) with three tabs:
.mp4 per bug, selectable from a list, each using
the captured screenshot as its poster.navigate / click / observe steps
per bug, reconstructed from the captured action log and sampled frames.Report the site path and open it. The report is a standalone static site — it is not served by the target app's dev server, so do not load it from the app's port (that returns 404). Either open the file directly:
open bug-report-site/index.html
or serve it on its own port and open the printed URL:
node report.mjs <findings-dir> --serve --port=7800
You may enrich each bug's reproduction steps in findings.json (from reading
the sampled frames/*.png) before regenerating the site.