Commit changes, create and merge a pull request, and close the linked GitHub issue.
npx skills add https://github.com/smallnest/goal-workflow --skill ship-it-smallnest
Please help me install this Agent Skill. Skill: ship-it Source: https://github.com/smallnest/goal-workflow/tree/main/skills/ship-it Command: npx skills add https://github.com/smallnest/goal-workflow --skill ship-it-smallnest
This Skill removes the repetitive final steps of delivering completed work, so you can turn a finished issue into a committed, reviewed, merged, and closed change without manual coordination.
Ask the ship-it skill to commit the completed changes, create and merge the pull request, and close the linked GitHub issue.
High-intent search queries and answers about installing and using this skill.
Automating a GitHub pull request and merge workflow involves staging issue-related files, committing with issue references, pushing the branch, opening a PR with closing keywords, and merging after status checks. This creates a traceable audit trail for shipped code.
To close a linked GitHub issue automatically after merging, include closing keywords in the pull request description. If GitHub's auto-close mechanism does not trigger, a fallback manual closure step ensures the issue is properly bookkept and marked complete.
The best way to commit and push only files related to a specific GitHub issue is to stage those specific changes selectively, create a commit message that references the issue number, and push the branch to the remote repository to prepare for pull request automation.
Yes, you need git and GitHub CLI installed to automate branch management, PR metadata creation, merge verification, and post-merge issue bookkeeping. These tools handle the required repository operations and API interactions for end-to-end shipping scenarios.
A GitHub issue stays open after a pull request is merged when auto-close does not occur, often due to missing or incorrect closing keywords in the PR description. A fallback manual closure step is required to add an implementation summary comment and close the issue.
Yes, you can verify PR status and add a post-merge implementation summary comment automatically by checking the pull request state, applying the chosen merge strategy, and generating a traceable audit trail comment on the closed issue.
pegasus-isiCreate GitHub issues from templates and initialize linked branches and worktrees.
SjdjdiejdrirhdkjejPromote validated staging builds to production with semantic versioning and health checks.
makoMakoGoAutomate GitHub issue-to-pull-request workflows with branch management and squash-merging.
aditriokaAutomate GitHub issue resolution and Pull Request creation via API.
