git-ship

Estrelas12

Forks2

Atualizado6 de março de 2026 às 13:16

Ships working changes: stage, commit, create PR via gh. Accepts --merge to squash-merge after PR creation, and --dry-run to preview without executing.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

hartphoenix

hartphoenix/weft

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

Programadores de computadorSOC 15-1251 Desenvolvedores de softwareSOC 15-1252

SKILL.md

readonly

name	git-ship
description	Ships working changes: stage, commit, create PR via gh. Accepts --merge to squash-merge after PR creation, and --dry-run to preview without executing.

/git-ship

Stage → commit → push → PR in one invocation.

Flags

Flag	Effect
`--merge`	Squash-merge the PR and delete the branch after creation
`--dry-run`	Show the plan without executing

Workflow

1. Preflight (parallel)

Run simultaneously:

git status
git diff --stat (staged + unstaged)
git log --oneline -5
git branch -a
git rev-parse --abbrev-ref HEAD
Detect default branch (main or master)
gh pr view --json state 2>/dev/null

Gate: if current branch already has an open PR, stop. Report: "Branch already has an open PR. Create a fresh branch for new changes."

Gate: if on main/master, stop. "Cannot ship directly to main. Create a feature branch first."

2. Group and filter changes

One coherent group: proceed
Mixed concerns: identify primary group, report the rest: "Skipping unrelated changes: [file list]"
Ambiguous: ask which changes to ship

Never stage .env, credentials, or secrets files.

3. Choose branch

On feature branch + changes fit       → stay
On feature branch + changes don't fit → find or create matching branch

Finding a match: scan local and remote branch names. Confirm with user before switching.

Creating: generate a descriptive slug (e.g., fix-auth-redirect). Confirm name with user. git checkout -b <slug>.

4. Commit

git add <file1> <file2> ... — name each file explicitly
Generate a concise commit message (1-2 lines) matching repo's recent style from step 1
Append Co-Authored-By: Claude <noreply@anthropic.com> trailer
Show the message, then commit immediately — do not wait for approval

5. Push + PR

Use AskUserQuestion: "Ready to push and open PR for <branch>." Options: Push / Abort. On abort, stop.

After confirmation:

git push -u origin <branch>
gh pr create — inferred title from branch name and commits, brief body summarizing changes. Report URL.

6. Merge (--merge flag only)

gh pr merge --squash --delete-branch
If merge fails (checks pending, review required): report status, stop
After merge: git checkout <default-branch> && git pull origin <default-branch>

Constraints

git add: explicit file names only — never -A, ., --all
git commit: stage first — never -a / --all
git push: only to origin — never to other remotes
No force-push
Never merge without --merge flag

Mais deste repositório

mesmo repositório

thischat

hartphoenix/weft

Returns the file path of the current session's JSONL log. With --stamp, adds provenance (session path + timestamp) to a file as YAML frontmatter (default) or HTML comment (--back). Use when a skill or agent needs to reference or annotate the current conversation's log file.

2026-03-2112

intake

hartphoenix/weft

Onboarding interview for the personal development harness. Scans background/ for pre-loaded materials (code, resumes, writing, transcripts), runs a conversational interview to discover background, goals, current skills, and learning preferences, then generates a personalized CLAUDE.md and initial current-state.md. Use when setting up a new learner, onboarding, or bootstrapping the harness.

2026-03-1012

progress-review

hartphoenix/weft

Cross-session learning pattern analysis. Reads multiple session logs and learning state to detect stalls, regressions, goal drift, and arc readiness that no single session review can see. Proposes updates to learning state files. Use when the user asks "how am I doing", "review my progress", "am I improving", or "progress review". Also dispatched automatically by startwork when enough sessions have accumulated.

2026-03-1012

session-digest

hartphoenix/weft

Returns a structured learning-state diff from session evidence without quizzing or writing files. Callers (session-review, startwork, or the user's main context) handle presentation, approval, and writes. Use when learning state is stale, before startwork, or when the user wants to update scores without a full session review.

2026-03-1012

session-discovery

hartphoenix/weft

Discovers Claude Code conversation sessions on the local machine within a date range. Returns a structured manifest of sessions with metadata. Use when a skill or agent needs to find prior conversations — e.g., session-review gathering evidence, progress-review windowing, or startwork checking recent activity. Not user-facing; designed as infrastructure for other skills.

2026-03-1012

safety-help

hartphoenix/weft

Audits Claude Code security configuration against the Safer YOLO guide. Checks sandbox, deny rules, hooks, DCG, and gitleaks. Surfaces findings in plain language with customized recommendations. Use when the user mentions YOLO mode, bypass permissions, skipping permissions, "dangerously-skip-permissions", security setup, or wants to harden their configuration.

2026-03-0712

name	git-ship
description	Ships working changes: stage, commit, create PR via gh. Accepts --merge to squash-merge after PR creation, and --dry-run to preview without executing.

/git-ship

Stage → commit → push → PR in one invocation.

Flags

Flag	Effect
`--merge`	Squash-merge the PR and delete the branch after creation
`--dry-run`	Show the plan without executing

Workflow

1. Preflight (parallel)

Run simultaneously:

git status
git diff --stat (staged + unstaged)
git log --oneline -5
git branch -a
git rev-parse --abbrev-ref HEAD
Detect default branch (main or master)
gh pr view --json state 2>/dev/null

Gate: if current branch already has an open PR, stop. Report: "Branch already has an open PR. Create a fresh branch for new changes."

Gate: if on main/master, stop. "Cannot ship directly to main. Create a feature branch first."

2. Group and filter changes

One coherent group: proceed
Mixed concerns: identify primary group, report the rest: "Skipping unrelated changes: [file list]"
Ambiguous: ask which changes to ship

Never stage .env, credentials, or secrets files.

3. Choose branch

On feature branch + changes fit       → stay
On feature branch + changes don't fit → find or create matching branch

Finding a match: scan local and remote branch names. Confirm with user before switching.

Creating: generate a descriptive slug (e.g., fix-auth-redirect). Confirm name with user. git checkout -b <slug>.

4. Commit

git add <file1> <file2> ... — name each file explicitly
Generate a concise commit message (1-2 lines) matching repo's recent style from step 1
Append Co-Authored-By: Claude <noreply@anthropic.com> trailer
Show the message, then commit immediately — do not wait for approval

5. Push + PR

Use AskUserQuestion: "Ready to push and open PR for <branch>." Options: Push / Abort. On abort, stop.

After confirmation:

git push -u origin <branch>
gh pr create — inferred title from branch name and commits, brief body summarizing changes. Report URL.

6. Merge (--merge flag only)

gh pr merge --squash --delete-branch
If merge fails (checks pending, review required): report status, stop
After merge: git checkout <default-branch> && git pull origin <default-branch>

Constraints

git add: explicit file names only — never -A, ., --all
git commit: stage first — never -a / --all
git push: only to origin — never to other remotes
No force-push
Never merge without --merge flag