yip-yip
From the author
Appa's "yip yip" for opening a pull request. Use at the end of every other workflow, and for "ship it", "open a PR", "open a pull request", "stack these PRs", or "write the PR description". Covers worktrees, commit shape, Conventional Commits titles, the PR description, forge choice, stacked PRs, and review-bot triage. Driving an open PR to merge-ready is `long-flight`.
Install
npx skills add tmcfarlane/team-avatar --skill yip-yip -a claude-code
Installs to .claude/skills/yip-yip/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- pr-descriptionmohitagw15856/pm-claude-skillsWrite a clear pull-request description that gets reviewed fast and merged with confidence, from a git diff, branch summary, or commit list. Use when opening a PR, summarizing a change for review, documenting code changes, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.Writing★ 1.5K
- open-prpascalorg/editorOpen or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.Writing★ 25.2K
- pr-writergetsentry/skillsCreate or refresh reviewer-facing PR titles and descriptions. Use when opening a PR, updating its title or body, or preparing branch changes for review.OfficialWriting★ 1.1K
- create-prhashgraph-online/awesome-codex-pluginsCreate a GitHub pull request from the current branch. Use when the user says 'create a pr', 'open pr', 'push and open a pr', 'create pull request', or wants to open a PR from their branch.Engineering★ 1.4K
- review-prtobihagemann/turboReview a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".Engineering★ 417
- creating-prMicrock/ordinary-claude-skillsUse when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practicesEngineering★ 408
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in