메뉴
Use this skill any time you are opening a PR to ship code or the user tells you to "ship it". It explains how to write PR bodies effectively and follow the style guide.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when navigating Wikipedia inside the split-pane extension—finding articles from a topic or phrase, teaching or routing the user toward articles, choosing what to explore next, Wikimedia REST or Action APIs with paging, or sending message_parent url_change (optional section `#fragment` on the same wiki). Use for Wikipedia search, summaries, links/backlinks, or updating the mirrored page URL.
Apply rich formatting to Notion pages - toggles, callouts, headers, and styled text. Use when creating or formatting Notion documents via the Notion MCP server.
Design and author Hermes Workflows with typed inputs/outputs, agent/bash/ask/parallel/pipeline/goal primitives, Review Queue gates, artifacts, and verification receipts. Use when creating or modifying workflow definitions.
Plan new software projects by decomposing the goal into MVP tasks, researching frameworks and libraries with subagents, and preferring opinionated prebuilt solutions over bespoke complexity. Use when starting a new project, scoping an idea, choosing a stack, or producing an implementation plan for a single-user MVP.
Draft or revise any kind of writing so it is clearer, better structured, and more effective for its audience. Use for essays, emails, memos, articles, narratives, speeches, social posts, marketing copy, personal writing, documentation, technical writing, reports, proposals, and mixed-format prose while preserving meaning and facts.
Zinsser-first plain writing style for any writing or editing task. Invoke before creating, editing, critiquing, rewriting, outlining, prompting, or polishing prose, docs, posts, proposals, teardown notes, social posts, emails, prompts, or skill instructions.**
| name | ship-it |
| description | Use this skill any time you are opening a PR to ship code or the user tells you to "ship it". It explains how to write PR bodies effectively and follow the style guide. |
NOTE: "Ship it" is a colloquialism for "open a PR" NOT merging a PR. You should never merge a PR with this skill.
Please move these changes to a new branch (if we are currently on main or a different feature's branch or outside a worktree), ensure pre-commit hooks pass, add one or more commits with brief commit messages, as appropriate, and open a PR. Your PR should provide a short but detailed summary of changes, as well as demonstrate (even with pseudo-code) any new DX features. Do not include a test summary or exhaustive list of changed files; the git diff is enough. Do not add "co-authored-by" lines to commit messages. Do not mention the tool (e.g. Claude) used to generate the commit message or PR.
Keep your PR body BRIEF and to the point.
