원클릭으로 Manus에서 모든 스킬 실행

ship-it

스타10

포크1

업데이트2026년 4월 1일 10:25

Create a GitHub PR with conventional format and AI session context. Use when user says 'create PR', 'open PR', 'submit changes', 'send to dev', 'ship it', or is done with their task.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

vltansky

vltansky/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create PR

Step 1: Check state

git branch --show-current && git status -s && git diff HEAD --stat

Detect username: git config user.name or extract from branch prefix
If on master/main/prod: create a feature branch:

git checkout -b <username>/<feature-name>

Branch name from the diff context — short, descriptive, kebab-case.

Step 2: Commit + Push

If uncommitted changes exist:

If staged files exist (respect user's selection):

git commit -m "<msg>" && git push -u origin HEAD

If no staged files (stage everything):

git add . && git commit -m "<msg>" && git push -u origin HEAD

Commit message: conventional format (feat:, fix:, refactor:, etc.), concise.

Step 3: Generate AI Session Context

Generate a privacy-safe summary for reviewers from the current conversation.

You already have full context of:

What problem was discussed
What approaches were considered
What decisions were made and why
What trade-offs were evaluated

Synthesize directly from your memory of this session.

What to include vs exclude

Include	Exclude
Problem being solved	Exact user prompts
Solution approach chosen	Mistakes/failed attempts
Key decisions + WHY	Debugging struggles
Trade-offs considered	Personal info/credentials
Technical rationale	Anything embarrassing

Format as collapsible block

<details>
<summary>AI Session Context</summary>

**Problem:** [1 sentence - what was broken/needed]

**Approach:** [1 sentence - solution strategy]

**Key Decisions:**
- [Decision]: [Rationale - the WHY]
- [Decision]: [Rationale - the WHY]

**Trade-offs Considered:**
- [Option A vs B]: Chose A because [reason]

</details>

Skip Conditions

Skip AI Session Context if:

Trivial change (typo, version bump, config)
No meaningful decisions were made
User says "no context" or "skip context"

Step 4: Create PR

Format:

<feature_area>: <Title> (80 chars max)

<TLDR> (1-2 sentences)

- bullet 1
- bullet 2

<details>
<summary>AI Session Context</summary>
...
</details>

gh pr create --title "<title>" --body "<body>"

Display the returned PR URL on its own line so it's clickable.

이 저장소의 다른 Skills

같은 저장소

hetzner-codex-remote

vltansky/skills

Prepare a Hetzner Cloud VPS for secure Codex remote SSH access. Use when the user wants to create or configure a Hetzner server for Codex remote control, fix "No codex found in PATH" on a remote machine, install agent development tooling on a VPS, harden SSH access to a Hetzner server, or connect the server through Codex Settings, Connections, Add SSH.

2026-05-1310

batch

vltansky/skills

Parallel work orchestration — decompose large changes into 5-30 worktree agents that each open a PR. Use when the user says 'batch', 'do this in parallel', 'split into PRs', 'bulk change', 'mass refactor', or wants a sweeping mechanical change across many files.

2026-05-1210

debug

vltansky/skills

Systematic root-cause debugging for any bug — backend, frontend, logic, integration. Hypothesis-driven investigation with evidence collection. Use when the user says 'debug', 'investigate', 'why is this broken', 'root cause', 'trace this bug', 'figure out why', 'this doesn't work', or 'unexpected behavior'. For frontend-specific runtime debugging with a log server, use /debug-mode instead.

2026-05-1210

fix-pr-comments

vltansky/skills

Handle feedback from PR reviewers. For each inline thread: reply on-thread and resolve after user approves. Use when developers left comments on your PR and you need to address them. Triggers on 'address comments', 'fix PR feedback', 'what did the reviewer say', 'handle review', 'resolve comments', 'comments from dev', 'dev feedback'.

2026-04-0110

grill-me

vltansky/skills

Structured adversarial review that pushes back on a plan, challenges the premise, compares alternatives, and stress-tests the design until the main risks are explicit. Use when the user asks to "grill me", stress-test a plan, poke holes in an approach, challenge assumptions, pressure-test a design, or validate an early-stage idea before building ("I have an idea", "is this worth building", "grill me on this idea").

2026-04-0110

rfc-research

vltansky/skills

Research a technical topic and produce an RFC document backed by real code evidence from GitHub. Use when user says 'write an RFC', 'RFC research', 'create RFC for', 'technical proposal', 'design doc', 'investigate X', 'research X and write a proposal', 'architecture decision record', 'ADR', or needs a structured technical decision document with prior art analysis.

2026-04-0110

name	ship-it
description	Create a GitHub PR with conventional format and AI session context. Use when user says 'create PR', 'open PR', 'submit changes', 'send to dev', 'ship it', or is done with their task.

Create PR

Step 1: Check state

git branch --show-current && git status -s && git diff HEAD --stat

Detect username: git config user.name or extract from branch prefix
If on master/main/prod: create a feature branch:

git checkout -b <username>/<feature-name>

Branch name from the diff context — short, descriptive, kebab-case.

Step 2: Commit + Push

If uncommitted changes exist:

If staged files exist (respect user's selection):

git commit -m "<msg>" && git push -u origin HEAD

If no staged files (stage everything):

git add . && git commit -m "<msg>" && git push -u origin HEAD

Commit message: conventional format (feat:, fix:, refactor:, etc.), concise.

Step 3: Generate AI Session Context

Generate a privacy-safe summary for reviewers from the current conversation.

You already have full context of:

What problem was discussed
What approaches were considered
What decisions were made and why
What trade-offs were evaluated

Synthesize directly from your memory of this session.

What to include vs exclude

Include	Exclude
Problem being solved	Exact user prompts
Solution approach chosen	Mistakes/failed attempts
Key decisions + WHY	Debugging struggles
Trade-offs considered	Personal info/credentials
Technical rationale	Anything embarrassing

Format as collapsible block

<details>
<summary>AI Session Context</summary>

**Problem:** [1 sentence - what was broken/needed]

**Approach:** [1 sentence - solution strategy]

**Key Decisions:**
- [Decision]: [Rationale - the WHY]
- [Decision]: [Rationale - the WHY]

**Trade-offs Considered:**
- [Option A vs B]: Chose A because [reason]

</details>

Skip Conditions

Skip AI Session Context if:

Trivial change (typo, version bump, config)
No meaningful decisions were made
User says "no context" or "skip context"

Step 4: Create PR

Format:

<feature_area>: <Title> (80 chars max)

<TLDR> (1-2 sentences)

- bullet 1
- bullet 2

<details>
<summary>AI Session Context</summary>
...
</details>

gh pr create --title "<title>" --body "<body>"

Display the returned PR URL on its own line so it's clickable.