Ship PR

    1

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

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 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).

    Requires GitHub CLI (gh) installed and authenticated. Cannot bypass manual approval step for PR creation. Branch naming follows specific ticket-based patterns.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill automates the transition from local code to a GitHub Pull Request by handling ticket-based branch naming, staging deployments, and template-driven PR generation in one sequence.

    You will need the GitHub CLI (`gh`) and `git` installed and authenticated on your local machine, as the skill uses these tools to securely manage remote operations.

    Yes, the skill is designed to work with your repository's existing `.github/PULL_REQUEST_TEMPLATE.md` or can provide a structured default format if one isn't present.

    The skill identifies your current branch, switches to the development/staging branch to merge and deploy, and then automatically returns you to your original working branch once the process is complete.

    No, the skill generates a draft PR for your review first; it will only finalize and submit the Pull Request to GitHub once you have explicitly approved the generated content.

    The skill works with any AI agent that has access to your local terminal and filesystem, provided the necessary GitHub CLI permissions are granted.

    New in DevOps & Cloud