Commit local git changes, push to a remote branch, and open a pull request.
npx skills add https://github.com/findexu/finpack-claude --skill ship-findexu
Please help me install this Agent Skill. Skill: ship Source: https://github.com/findexu/finpack-claude/tree/main/plugins/setup-finpack/template/skills/ship Command: npx skills add https://github.com/findexu/finpack-claude --skill ship-findexu
This Skill helps you publish your work by turning local changes into a commit, pushing to a remote branch, and opening a pull request—while requiring explicit confirmation before each high-impact action.
Use the ship skill to commit, push, and open a PR for your current branch with confirmation at each step.
High-intent search queries and answers about installing and using this skill.
To ship local git changes safely, the workflow scans your working tree, proposes a staging set, creates a commit, pushes to a remote branch, and opens a pull request with explicit confirmation before each high-impact action. It prevents staging secrets and build artifacts.
Safe staging requires scanning modified, added, deleted, and untracked files to propose exactly which to stage. This mechanism prevents staging common secrets, lock files, generated artifacts, and dependency directories, ensuring you know exactly what will be shipped.
Guided pull request creation checks upstream configuration, avoids force-push, and verifies whether a PR already exists. It then drafts and creates a PR with a confirmed title and body, requiring explicit confirmation before submitting the PR.
Yes, creating a pull request from your local branch requires the GitHub CLI. The workflow uses gh pr view and gh pr create commands to verify existing PRs and draft or submit new ones safely without skipping confirmation steps.
No, this deployment workflow requires explicit confirmation before committing, pushing, and creating the PR. It validates against risky file patterns to ensure safe publication, meaning you cannot skip these confirmation steps during the code publishing process.
Your git push may fail if upstream configuration is incorrect or if the workflow prevents a force-push. The process checks upstream settings and avoids force-push to protect the remote branch, requiring you to verify configuration before proceeding.
gajjalaashok75-UIStages modified files, commits conventionally, and pushes to remote tracking repository.
arjitj2Squash-merge approved Dependabot pull requests sequentially with conflict resolution.
uxnameRun npm checks, stage changes, and create conventional git commits.
jiunbaeAutomate secure Git commits and PR creation with security and style checks.
