菜单
Commit changes in logical units and create a Draft PR assigned to riseshia. Creates a new branch if on the base branch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit Claude-authored commits across all repositories Claude has worked in against the code-style guide, reporting violations plus guide defects (missing, dead, or ambiguous rules) the violations reveal. Run on demand from the dotfiles (marketplace) repo.
riseshia's coding conventions. Use it always unless a project-specific convention (CLAUDE.md, style guides) exists.
Quality-check the code-style guide for contradictions, duplications, and ambiguous rules. Run after editing the code-style skill files.
Explain a topic as a single, readable, self-contained HTML file that the user opens in a browser. Use when the user runs /explain-with-html, or asks to have something explained "as HTML", "in a browser", or with a visual/diagram-heavy write-up. The topic is optional — infer it from the recent conversation and confirm before generating. Use mermaid.js for diagrams when they help.
Run a development task as an event-driven state machine (plan → plan-approve → implement → validate → minor-fix/recheck → open-pr → followup → retrospect → done). A thin orchestrator fires named transitions via a CLI that enforces the plan-approve human gate and bounded rework/continue loops, reads a per-state prompt for each node, delegates heavy work-states to fresh workers (Agent tool or claude -p) over a file-based handoff, and ships via a Draft PR. Use when the user wants to run a non-trivial task end-to-end with minimal supervision.
High-precision code review inspired by Alibaba Open Code Review. Script-driven pre-processing, per-file isolated review, three-layer false-positive reduction.
| name | draft-pr |
| description | Commit changes in logical units and create a Draft PR assigned to riseshia. Creates a new branch if on the base branch. |
| user_invocable | true |
Commit work in progress and create a Draft PR assigned to riseshia.
Follow these steps in order.
git branch --show-current
If on a base branch (staging, main, or master), create a new branch first.
Choose a branch name based on the changes. Naming convention:
fix/<brief-description>feature/<brief-description>refactor/<brief-description>docs/<brief-description>chore/<brief-description>git checkout -b <branch-name>
git status
git diff
git diff --cached
Review both staged and unstaged changes.
Commit changes in logical units.
Commit guidelines:
Commit message and PR language: Use the repository's primary language (determined by recent commit messages), not the conversation language. Check with git log --oneline -10 and match the style.
git add <specific-files>
git commit -m "$(cat <<'EOF'
<commit message - in the repo's primary language>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
EOF
)"
git push -u origin <branch-name>
Write the PR title and body in the repository's primary language.
gh pr create --draft --assignee riseshia --title "<PR title>" --body "$(cat <<'EOF'
## Summary
- <list of changes>
## Test plan
- [ ] <test items>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Display the created PR URL to the user.