Ship PR

    1

    Branch, dev deploy, PR draft review, then gh pr create, with your approval before the PR opens

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Ship PR

    Example session with this skill installed

    I've finished the login fix for ticket AUTH-456. Create a branch, deploy it to develop, and open a PR to main.

    • Read your context and instructions
    • Compiled the ship pr

    I will now handle the deployment and PR process for AUTH-456.

    1. Created and pushed branch feat/AUTH-456-login-fix.
    2. Merged changes into develop to trigger the dev server deployment.
    3. Switched back to feat/AUTH-456-login-fix.
    4. Generated the PR draft below.

    Pull Request Draft

    Title: [AUTH-456] fix: resolve session timeout issue on login
    Base: main
    Head: feat/AUTH-456-login-fix

    Body:

    
## Prerequisite PRs
None

## Changes
- Fixed race condition in session storage initialization
- Added error handling for expired tokens during login flow
- Updated unit tests for authentication provider

## Links
- Issue: https://my-org.atlassian.net/browse/AUTH-456

## Notes
Verified on local build; requires verification on dev environment.

    Next steps

    • Review the PR title and body above.
    • Confirm if you want to proceed with gh pr create.
    • Check the dev server logs to ensure the deployment was successful.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    A small, predictable shipping routine for when a feature or fix is committed and ready for review:

    1. Create the branch following your naming convention (default feat/<TICKET>-<short-description>).
    2. Deploy to dev by merging into your dev branch and pushing, or by running your deploy command, then returning to the working branch.
    3. Draft the PR (title [<TICKET>] feat: ..., changes, issue link, notes) and show it to you first. It uses your repo's .github/pull_request_template.md if one exists.
    4. Create the PR with gh pr create, only after you approve the draft.

    Configurable

    A short placeholder table sets the ticket format, branch pattern, PR base branch, dev branch, and issue-tracker URL. Values in your repo's CLAUDE.md or CONTRIBUTING.md take precedence. If something is unknown, the agent asks once before starting.

    Guardrails

    • The PR base is always your main branch, never the dev branch.
    • No PR is opened without an explicit OK on the draft.
    • Keeps the ticket key in the branch name for repos whose bots require it.

    Requirements

    Git and an authenticated GitHub CLI (gh).

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 5 days ago

    • Free to download with an account

    Listed5 days ago

    What's inside

    Frequently Asked Questions