Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentsmesh/gh-merge
Completes the AgentsMesh GitHub pull-request workflow: commits scoped changes, rebases on the authoritative GitHub branch, opens or reuses a PR, monitors required checks, fixes failures, and merges only after verification.
Passed 16 of 19 test cases with the skill, and 10 of 19 without it.
and 4 more in the full report
6 fixed12 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
After resolving rebase conflicts against an updated target base branch, what step must be taken before pushing the updated branch?
| Checked | Without skill | With skill |
|---|---|---|
| Reruns local tests after completing the rebase | Missed | Passed |
The instructions your model reads when the skill loads.
GitHub is the development source of truth for this repository. Land changes through a GitHub pull request; do not create a GitLab merge request for product code.
Inspect repository state:
git status --short --branch
git branch --show-current
git remote -v
gh auth status --hostname github.com
Identify the GitHub remote by URL instead of assuming a remote name. Resolve
the target branch, normally main, and refuse to merge directly while
checked out on that branch.
Review all dirty files. Stage only files belonging to the requested change;
preserve unrelated user changes and never use git add .. Run the relevant
local tests and git diff --check, then create a focused commit containing
only the requested change.
Require a clean index and working tree before rebasing. If unrelated user changes remain, do not stash or move them automatically; use an already isolated checkout or stop and report what prevents a safe rebase. Once the checkout is clean, fetch and rebase on the current GitHub target:
git fetch <github-remote> <target-branch>
git rebase <github-remote>/<target-branch>
Resolve conflicts with user-owned work preserved, then rerun affected tests when the rebase changes the integration base.
Push the current branch. After a rebase, use --force-with-lease, never
--force.
Reuse an existing pull request for the branch or create one with gh pr create and the repository PR template. The title and body must explain
test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.