chess-teacher-merge-develop

Automates opening, CI-monitoring, and merging feature-branch pull requests into develop via GitHub CLI.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/daniel-brus/chess_teacher --skill chess-teacher-merge-develop-daniel-brus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chess-teacher-merge-develop
Source: https://github.com/daniel-brus/chess_teacher/tree/main/.agents/skills/chess-teacher-merge-develop
Command: npx skills add https://github.com/daniel-brus/chess_teacher --skill chess-teacher-merge-develop-daniel-brus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Finishing a feature branch involves repetitive manual steps: pushing to the remote, opening a PR against the correct base, applying the right version-bump label, babysitting CI checks, and merging only when green. This Skill orchestrates that entire feature-to-develop flow so nothing is forgotten or merged prematurely. ## Core Features & Use Cases - PR orchestration: Opens or reuses a pull request targeting develop, never main, using the gh CLI. - Bump label enforcement: Ensures exactly one of bump:patch, bump:minor, or bump:major is set, defaulting to the smaller label when uncertain. - CI babysitting loop: Polls check status via scripts/pr_status.py, fixes clear failures (up to 3 push cycles), and reports back with diagnostics when blocked instead of guessing. - Use Case: You finished a bugfix branch and say "merge this to develop" — the agent pushes the branch, opens the PR, applies bump:patch, waits for CI to go green, merges, and reminds you that CD publishes the development image. ## Quick Start Ask the agent to merge the current feature branch into develop and finish the PR.

Frequently Asked Questions about chess-teacher-merge-develop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a feature branch into develop with GitHub CLI?▼

Push the branch to origin, create a PR with gh pr create --base develop, wait for checks to pass with gh pr checks, then run gh pr merge <N> --merge. This Skill automates that full sequence including label and CI handling.

How do I fix a failing CI check on a pull request?▼

Pull the failing job logs with gh run view <id> --log-failed, fix only clear errors caused by the PR, commit and push to the remote feature branch, then re-poll checks. The Skill caps automatic fix attempts at 3 push cycles before reporting back.

Can this Skill merge a pull request into main or production?▼

No. The base branch is always develop and the Skill explicitly refuses to create or merge PRs to main. Production releases are out of scope and must be handled through a separate manual release process.

What bump label should I use for a pull request?▼

Use bump:patch for bugfixes, tests, chores, and docs; bump:minor for clear user-visible features; bump:major for breaking API, data, or deploy changes. When in doubt, choose the smaller label, defaulting to bump:patch.

Why does CI not reflect my local commits on the PR?▼

CI builds the remote feature branch, not your local HEAD. Local-only commits never trigger checks, so you must git push before trusting PR status. The Skill verifies divergence between HEAD, origin/<feature>, and origin/develop before relying on CI.