Merge feature branches and create structured GitHub pull requests.
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-ship-hidonguyen
Please help me install this Agent Skill. Skill: ck:ship Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/ship Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-ship-hidonguyen
This Skill eliminates the manual, error-prone steps required to land a feature branch by automating pre-flight checks, merging the target branch, running tests and reviews, bumping versions, updating changelogs, and creating a structured pull request so teams can release reliably and consistently.
Run the ck:ship command from your feature branch to execute the full pipeline and return the created PR URL.
High-intent search queries and answers about installing and using this skill.
To automate creating a GitHub pull request from a feature branch, you can use a pipeline that merges the target branch, runs tests, bumps versions, updates changelogs, and opens the PR. This ensures merges, reviews, and PR creation execute in a consistent, auditable sequence.
An automated release pipeline handles version bumps and changelog updates by auto-detecting your version and changelog files, generating new changelog entries, and composing conventional commits. It distinguishes between official and beta releases to apply the correct versioning automatically.
Yes, you need the GitHub CLI (gh) installed and authenticated to automate pull request creation. The pipeline requires git access and the gh CLI to execute pre-flight checks, merge target branches, and create or update structured PRs directly from your feature branch.
Yes, you can run automated code reviews and tests before merging a feature branch. The pipeline delegates heavy tasks to subagents, executing a tester subagent for tests and a code-reviewer subagent for pre-landing checks to validate your code before creating the PR.
The best way to manage background tasks like updating technical journals and docs during a release is to execute them as non-blocking background tasks. This delegates heavy work to subagents, saving tokens and avoiding inlining test or review logic while the main pipeline proceeds.
Yes, an automated ship pipeline works with multi-language repositories and CI workflows. It auto-detects your test runner, version files, and default branches to apply the correct merging, testing, and release behaviors across different language stacks and CI configurations.
aayushsoamAutomate GitHub Pull Request lifecycle from branch creation to merging.
ajsai47Merge GitHub pull requests and verify production health after deployment.
garrytanAutomates merging, testing, versioning, changelog updates, and generating pull requests for your current branch.
LllooogggCreate pull requests from dev to main with version bumps and auto-merge.
