Menú
Scan changes, commit, push, and create a PR. With confirmation at each step
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Investigate a non-trivial task before planning. Produces a findings report with file:line citations covering current behavior, upstream/reference equivalents, framework bridges, helpers to reuse, and open questions. Use before porting an upstream change, migrating a screen to Compose, touching unfamiliar modules, or any cross-cutting change. The point is to ground the plan in evidence, not memory.
Trim verbose prose, walls of text, journey narration, and WHAT comments from docs and code without losing vital info. Targets markdown files (docs, CLAUDE.md, rules, skills, agents) and, when asked, code comments / KDoc. Applies the "WHY not WHAT" rule, the "describe current behavior not the journey" rule, and the "release notes not implementation rationale" rule from `.claude/rules/workflow.md` and `.claude/rules/code-quality.md`. Use after a feature lands and the docs around it have accumulated cruft, or when a file feels heavier than it earns. Always plans before editing.
Find and fix a bug. Default is careful (reproduce, investigate, test). Add `--fast` for emergency production mode (hotfix branch, minimal change, ship a PR fast).
Audit a Reikai feature ported onto Mihon for behavioral parity against the Yōkai-era source on the `design/library-compose` branch. Use when the user asks to audit, verify, or sanity-check a ported feature, when they want to know whether a port "really matches" the original, or when they want a defect-fix pass on a recently-ported area. Takes a scope argument like "novel reader" or "Settings → Security". Compares features and behavior only, NOT pixels or layout (the user often redesigns visuals on the way over).
Deep, fan-out research over the codebase to answer a big question (test gaps, how a subsystem works end to end, a risk/security/dead-code audit, "where does X happen everywhere"). The codebase analog of deep web research: parallel explorer agents gather file:line-cited findings, surprising or high-stakes claims are adversarially verified against current code, and the result is a single prioritized report. Use for broad/deep questions that span many files and modules, NOT a one-file lookup and NOT a single-task pre-plan (use /scout for that, /explain for one thing).
Estimate per-turn token cost of this project's `.claude/` configuration and `CLAUDE.md`. Reports always-loaded vs path-scoped vs invoked-only, ranks the top contributors, and flags entries over budget. Add `--api` for exact counts via Anthropic's count_tokens endpoint instead of the chars/4 heuristic.
| name | ship |
| description | Scan changes, commit, push, and create a PR. With confirmation at each step |
| argument-hint | [optional commit message or PR title] |
| disable-model-invocation | true |
| allowed-tools | ["Bash(git status)","Bash(git diff *)","Bash(git log *)","Bash(git add *)","Bash(git commit *)","Bash(git push *)","Bash(git checkout *)","Bash(git branch *)","Bash(gh pr create *)","Bash(gh pr view *)"] |
Ship the current changes through commit, push, and PR creation. Confirm with the user before each step using the AskUserQuestion tool.
git status to see all changed, staged, and untracked filesgit diff to see what changed (staged + unstaged)git log --oneline -5 to see recent commit style.env*, *.pem, *.key, credentials.jsonpackage-lock.json, yarn.lock, pnpm-lock.yaml (unless intentionally updated)*.gen.ts, *.generated.*, *.min.js, *.min.cssdist/, build/, .next/, __pycache__/node_modules/, vendor/, .venv/.DS_Store, Thumbs.db, *.swp, .idea/, .vscode/settings.jsonCo-Authored-By lines in the commit message — this project explicitly forbids themgit push -u origin <branch>Check if a PR already exists for this branch with gh pr view --repo unseensnick/Reikai. If it exists, show the URL and stop.
Analyze ALL commits on this branch vs the base branch (not just the latest commit)
Draft a PR title (under 72 chars) and body with:
## Summary: 2-4 bullet pointsDo NOT include a ## Test plan section — verification before opening is implicit on this solo fork
Do NOT include 🤖 Generated with [Claude Code] or any other AI-attribution footer
ASK the user to confirm or edit the title and body
Only after confirmation, create the PR with:
gh pr create --repo unseensnick/Reikai --base main --title "…" --body "…"
The repo is standalone (not a fork) and gh's default repo is set to unseensnick/Reikai, so gh pr create already targets it; the --repo unseensnick/Reikai --base main flags are kept for explicitness and remain safe to pass.
Show the PR URL when done