nixos-config

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.

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.

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.

Split current changes into meaningful Git commits, then push to remote. Use when asked to commit and push.

Split current changes into meaningful Git commits. Use when asked to commit, make a commit, or split changes into commits.

Autonomous execution helper for OpenSpec tasks. Checks change readiness, then selects execution method based on task size: ralph-loop (small) or ralph-tui (large). Triggers: 'run tasks autonomously', 'ralph run', 'opsx:run', 'auto-execute', 'loop execute', 'run with ralph'

Save web documentation and external resources as markdown files for reference. Use when researching libraries/APIs ("read the documentation of X", "check the docs for Y"), after web searches to preserve useful pages, or when planning tasks that need external references. Saves to external-docs/ directory in the git repository root.

Use this skill to review code changes for quality, best practices, potential bugs, security issues, and performance improvements. Triggers on requests like "review this code", "check for issues", "code review", or after completing large changes.

Use this skill when the user asks to query Codex ("codexに聞いて", "codexで調べて", "codexにレビューを依頼", "ask codex", "consult codex", "codex review") for technical questions, code reviews, code analysis, architecture discussions, best practices, or implementation guidance. Handles interaction with the Codex CLI tool.