菜单
Create an HTML report to review the current session's changes. Include screenshots when changes affect UI/visuals. Use when the user asks for a review report, session summary as HTML, or visual diff of changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reorganize messy git commit history on a feature branch into clean, reviewer-friendly commits. Use when: user says "コミットを整理", "organize commits", "squash commits", "clean up history", "rewrite commits", or wants to prepare a branch for PR review by removing trial-and-error noise. Handles soft reset, logical grouping, and recommitting with clear messages.
Safely rebase the current branch onto the latest origin/main. Stashes uncommitted work, fetches, rebases, and restores.
Reviews changed code for reuse, quality, and efficiency, then fixes issues found. Preserves all functionality.
Capture screenshots of the current work-in-progress UI via agent-browser against a running local dev server, then open them with google-chrome-stable. For UI changes, capture before/after pairs (and Figma reference shots when a design URL is provided) so visual diffs can be reviewed at a glance.
Fetch and display comments from the current GitHub pull request. Use when asked to show PR comments, review comments, or check PR feedback.
Create a branch, commit changes, push to remote, and create a pull request. Use when asked to create a PR or pull request.
| name | session-review-report |
| description | Create an HTML report to review the current session's changes. Include screenshots when changes affect UI/visuals. Use when the user asks for a review report, session summary as HTML, or visual diff of changes. |
| disable-model-invocation | true |
Generate a self-contained HTML report summarizing the changes made during the current session, so the user can review them in a browser.
Write the report to the scratchpad directory:
<scratchpad>/session-review-<short-timestamp>.html
After writing, print the absolute path and (optionally) open it with google-chrome-stable <path> & in the background.
If the user mentions "artifact" / "アーティファクト" / "共有" / "share" / wanting to share the report (or otherwise asks for a hosted/shareable version), also publish it via the Artifact tool:
Artifact."📝" for session reviews) and reuse it on redeploys.<!doctype> / <html> / <head> / <body> tags before publishing — the Artifact harness wraps them in.Do not upload to Artifact by default — only when the user explicitly asks for it.
git status --shortgit diff (working tree + staged)git log --oneline <session-base>..HEAD if commits were made.tsx, .jsx, .vue, .svelte, .css, .scss, design tokens, theme configs)take-screenshot skill or invoke agent-browser screenshot <path> directly<img src="..."><pre>), Screenshots (only if captured), Next steps / open questionsWrite tool, then print its path.