메뉴
Safe git-to-PR workflow. Classifies changes, stages by explicit filename, runs final-pass checks, commits with approval, pushes, creates PR via gh. Encodes all git safety rules. Use when ready to ship code as a PR.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/robert-chiniquy/dotfiles --skill git-create-pr명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Sweep open issue trackers, TODOs, active branches, and source evidence to find narrowly scoped, independent, verifiable tasks suitable for remote agents or parallel delegation. Use when asked to find pebbles, small delegatable work, fire-and-forget candidates, backlog slices, ready items, or pool/task combinations.
Write a scorecard — a dark, skimmable one-screen readout of the current situation in the user's work, rendered as a terminal (TUI) artifact by the `scorecard` binary from a structured markdown file. Use ONLY when the user explicitly asks for a scorecard (or a "readiness card" / "go/no-go card" / "coverage snapshot card"). A plain "status", "status?", or other status/situation question gets a prose answer, never this skill. NOT a web page — output is the dark TUI. Preserves older scorecards by datestamp. Triggers on: scorecard, readiness card, go/no-go card, coverage snapshot card.
Present comparisons as narrow ASCII bar charts in the terminal. Use when user asks to compare items, metrics, counts, or coverage between things.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | git-create-pr |
| disable-model-invocation | true |
| description | Safe git-to-PR workflow. Classifies changes, stages by explicit filename, runs final-pass checks, commits with approval, pushes, creates PR via gh. Encodes all git safety rules. Use when ready to ship code as a PR. |
| allowed-tools | ["Read","Grep","Glob","Bash","AskUserQuestion","Agent","Skill"] |
Complete workflow from dirty working tree to open pull request.
rch/<type>/<topic>git status to see all changesgit diff --stat to see scopePresent the classification to the user. Ask if any files should be excluded.
Run /git-final-pass on the changes. Fix any failures before proceeding.
If the project has:
make lint, golangci-lint run, npx eslint, etc.)make test, go test ./..., npm test, etc.)make check, npx tsc --noEmit, etc.)All must pass before proceeding. Do not skip failing checks.
Stage files by explicit name. Never use git add -A or git add .
git add path/to/file1.go path/to/file2.go path/to/file2_test.go
Verify staged files match the classification from Phase 1:
git diff --cached --name-only
Draft a commit message:
Show the message to the user. Ask "ready to commit?" and wait for approval.
Check if branch tracks a remote:
git rev-parse --abbrev-ref @{upstream} 2>/dev/null
If not, push with -u:
git push -u origin HEAD
Ask "ready to push?" and wait for approval. Never push without asking.
Use gh pr create:
gh pr create --title "title" --body "$(cat <<'EOF'
## What
Brief description of changes.
## Why
Motivation and context.
## Test plan
How to verify this works.
EOF
)"
Return the PR URL to the user.
git add -A or git add . — stage files explicitly--force, --force-with-lease) without explicit instruction--no-verify)fmt.Println, console.log, print() in staged diff