菜单
Git workflow: commit, push, and create/update a draft PR. If a PR exists for the current branch, update its body. Trigger: 'commit push pr', 'ship it', 'send a PR', or /commit-push-pr.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Decompose a piece of an existing codebase — a function, method, class, or module — into a runnable notebook that explains it top-down: a call-graph map, then each piece defined and executed on concrete mock inputs with its real output shown inline. Turns code you didn't write (or have forgotten) into an interactive, line-by-line walkthrough. Use this skill only when the user explicitly invokes it by name (`explain-as-notebook`) or near-match mentioning.
Analyze the agent experience ("AX") of an interface an AI agent drives — a CLI, MCP server, HTTP/REST API, or library/SDK — against the principles of what makes a system easy for a reasoning-loop agent to use, and prescribe prioritized fixes. Use this skill only when the user explicitly invokes it by name (`ax-interface-analysis`) or near-match mentioning.
Reverse-engineer and document the user-facing API and UX/DX of an existing or cloned codebase — the system as seen from outside the boundary, whether the "user" is an end user or a developer. Use this skill only when the user explicitly invokes it by name (`explain-ux-dx-design`) or near-match mentioning.
Reverse-engineer and document the data architecture of an existing or cloned codebase — where data rests (stores, schema) and how it moves (dataflow, lineage). Use this skill only when the user explicitly invokes it by name (`explain-data-architecture`) or near-match mentioning.
Reverse-engineer and document the architecture of an existing or cloned codebase. Use this skill only when the user explicitly invokes it by name (`explain-system-architecture`) or near-match mentioning.
Reference for the DCMTK (OFFIS DICOM Toolkit) command-line tools — the canonical CLI for working with DICOM files and DIMSE network services. Use when converting, dumping, anonymizing, or validating DICOM files, or running DIMSE services (C-ECHO/STORE/FIND/MOVE/GET), worklists, or structured reports from the terminal.
| name | commit-push-pr |
| description | Git workflow: commit, push, and create/update a draft PR. If a PR exists for the current branch, update its body. Trigger: 'commit push pr', 'ship it', 'send a PR', or /commit-push-pr. |
| metadata | {"version":"2026-06-12"} |
Run in parallel:
git status, git diff, git diff --staged, git log --oneline -10git branch --show-current, git rev-parse --abbrev-ref @{upstream} 2>/dev/nullgh auth statusgh pr list --head $(git branch --show-current) --json number,title,isDraft,url --limit 1Hard stops:
gh auth status fails. Report a clear fix (e.g., run gh auth login).main or master.Skip steps that aren't needed (e.g., nothing to commit → skip to push).
git add -A or git add .).env, credentials, tokens)git push -u origin HEAD; otherwise git push.release/*, protected remote branches), ask for explicit confirmation before pushing.git log --oneline BASE..HEAD and git diff BASE...HEAD --stat--body-file (avoid inline multi-line shell quoting)gh pr create --draft with title (<70 chars) and body summarizing all commits since basegh pr edit --body-file incorporating new changes; keep title unless outdated## Summary + bullet points + ## Test plan checklist. Scale detail to change size.Before push/PR, run project checks when available (e.g., test/lint/typecheck). If checks fail, report and ask whether to proceed.
Show: commit hash/message (if any), clickable PR URL, whether PR was created or updated, and whether checks passed/skipped.