⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.0.0

gentle-ai-branch-pr

gentleman-programming@gentleman-programming⭐ 9.0k stars· last commit 3d ago· 366 open issues

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 9.0k on GitHubGitHub ↗

Very popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

https://github.com/user-attachments/assets/fa5c0cfe-06e7-4c0d-bd6e-8ac7cb934339

https://github.com/user-attachments/assets/6d2bc422-a4dd-4ecf-a04b-fcd3bea7fea9

If Gentle-AI made your agent worth trusting, a star helps other people find it.

WORKS WITH THE AGENT YOU ALREADY HAVE

Pi · OpenCode · Claude Code · Codex · Cursor · VS Code Copilot · Gemini CLI · Kilo Code Kimi Code · Kiro IDE · Qwen Code · Hermes · Antigravity · Windsurf · OpenClaw · Trae · Conductor

17 integrations · native configuration · compare capabilities →

Support the project

Sponsorship never buys rankings, default selections or endorsements; see TRADEMARKS.md.

Features


Engram™ — Keep your project context

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/branch-pr/SKILL.md7.9 KBupstream ↗
    ---
    name: gentle-ai-branch-pr
    description: "Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review."
    license: Apache-2.0
    metadata:
      author: gentleman-programming
      version: "2.0"
    ---
    
    # Gentle AI — Branch & PR Skill
    
    ## When to Use
    
    Load this skill whenever you need to:
    - Create a branch for a new fix or feature
    - Open a pull request on [Gentleman-Programming/gentle-ai](https://github.com/Gentleman-Programming/gentle-ai)
    - Prepare changes for review
    
    ## Critical Rules
    
    1. **Every PR MUST visibly link an approved base-repository issue** — `Closes/Fixes/Resolves #<N>` closes it on merge; `Refs #<N>` is non-closing. Every accepted reference MUST have `status:approved`; malformed, cross-repository, or mixed closing/non-closing references for the same issue are rejected by CI.
    2. **Ordinary `type:*` categorization** — CI rejects zero or multiple type labels. Route it through the canonical issue-creation workflow contract: a current direct human instruction binds the exact target/action, target-host capability is verified, and it uses one bounded mutation and target-host readback; otherwise wait without mutation.
    3. **Protected policy labels** — Adding or removing `status:approved` or `size:exception` requires authenticated actor target-host `viewerPermission` `MAINTAIN` or `ADMIN` and a current direct human instruction binding the exact target/action. Here verified policy authority means that actor permission and exact direct instruction, not separate target-host proof of the instruction-giver's identity; do not mutate automatically. `size:exception` additionally requires documented over-budget rationale and a human-selected exception.
    4. **400-line review budget** — keep PRs within 400 changed lines (`additions + deletions`) or document the rationale required for a `size:exception` label.
    5. **REQUIRED checks must pass** — establish requiredness from the target branch rulesets/branch protection and current run status; see Automated Checks below.
    6. **No `Co-Authored-By` trailers** — never add AI attribution to commits.
    7. **No force-push to main/master** — protected branch.
    
    ## Workflow
    
    Before any target-host read, obtain explicit authorization for the remote destination (exact target), operation (including metadata/status reads), and credential/session. Do not probe ambient credentials. After authorization reuse fresh target-bound approved-issue, default branch, `type:*` label and check evidence rather than re-asking verified facts. Missing or stale evidence remains unknown.
    
    1. Confirm the base-repository issue has `status:approved` on the authorized target. Resolve its current default/base branch from target metadata; do not assume `main`.
    2. Ask the human whether the PR should close the issue on merge. Preserve the human-selected `Closes/Fixes/Resolves #N` closing intent or `Refs #N` non-closing intent; do not substitute one for the other.
    3. Implement authorized work and run applicable local checks. Do not auto commit, push, create a PR, merge, select a chain strategy or exception, or give native RDD consent. Each operation needs its own human authority.
    4. Draft against the template. Declare one `type:*` result; any label mutation follows the canonical issue-creation workflow contract and exact direct instruction. Mark checkboxes only after observed readback.
    5. Determine REQUIRED CI from current target branch rulesets/branch protection and current run status before calling a PR merge-ready. CodeRabbit is optional unless target policy makes it required; a pending optional run is not a blocker. Unknown requiredness is not merge-ready.
    
    For baseline attribution compare the same failing command/environment on a comparable isolated clean base, without disturbing user changes. If not compared, report baseline unverified; do not use stash/pop.
    
    ---
    
    ## Branch Naming
    
    Branch names **must** match this pattern:
    
    ```
    ^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)\/[a-z0-9._-]+$
    ```
    
    | Type | Example |
    |------|---------|
    | `feat/` | `feat/user-login` |
    | `fix/` | `fix/duplicate-observation-insert` |
    | `docs/` | `docs/api-reference-update` |
    | `refactor/` | `refactor/extract-query-sanitizer` |
    | `chore/` | `chore/bump-bubbletea-v0.26` |
    | `style/` | `style/fix-linter-warnings` |
    | `perf/` | `perf/optimize-catalog-loading` |
    | `test/` | `test/add-pipeline-coverage` |
    | `build/` | `build/update-goreleaser-config` |
    | `ci/` | `ci/add-e2e-docker-job` |
    | `revert/` | `revert/undo-model-picker-change` |
    
    **Rules:**
    - All lowercase
    - Use hyphens, dots, or underscores as separators (no spaces, no uppercase)
    - Description must be short and descriptive
    
    ---
    
    ## PR Body Format
    
    Use the current `.github/PULL_REQUEST_TEMPLATE.md` as authority. The following is a non-executable schematic, not a complete PR body or a publication command. Include all sections required by the actual template (including Automated Checks and Notes for Reviewers when present). Fill only observed facts, leave unverified boxes unchecked and record pending actions separately.
    
    ```markdown
    ## 🔗 Linked Issue
    
    <human-selected Closes/Fixes/Resolves #N or Refs #N> (closing vs non-closing intent must be asked, not inferred)
    
    ## 🏷️ PR Type
    
    - [ ] `type:bug` — Bug fix (non-breaking change that fixes an issue)
    - [ ] `type:feature` — New feature (non-breaking change that adds functionality)
    - [ ] `type:docs` — Documentation only
    - [ ] `type:refactor` — Code refactoring (no functional changes)
    - [ ] `type:chore` — Build, CI, or tooling changes
    - [ ] `type:breaking-change` — Breaking change
    
    ## 📝 Summary
    
    <!-- Clear description of what this PR does and why. -->
    
    ## 📂 Changes
    
    | File / Area | What Changed |
    |-------------|-------------|
    | `path/to/file` | Brief description |
    
    ## 🧪 Test Plan
    
    <!-- Replace examples below with commands actually run and their observed outcomes. -->
    
    **Unit Tests**
    \`\`\`bash
    go test ./...
    \`\`\`
    
    **Go Format**
    \`\`\`bash
    go run ./internal/gofmtcheck
    \`\`\`
    
    **E2E Tests** (Docker required)
    \`\`\`bash
    cd e2e && ./docker-test.sh
    \`\`\`
    
    - [ ] Unit tests pass (`go test ./...`)
    - [ ] Go format passes (`go run ./internal/gofmtcheck`)
    - [ ] E2E tests pass (`cd e2e && ./docker-test.sh`)
    - [ ] Manually tested locally
    
    ## ✅ Contributor Checklist
    
    - [ ] PR is linked to an issue with `status:approved`
    - [ ] PR stays within 400 changed lines, or the human-selected `size:exception` rationale, current direct human instruction for the exact target/action and actor `MAINTAIN`/`ADMIN` are documented
    - [ ] API read-back confirms exactly one appropriate `type:*` label on this PR
    - [ ] Unit tests pass (`go test ./...`)
    - [ ] E2E tests pass (`cd e2e && ./docker-test.sh`)
    - [ ] I have updated documentation if necessary
    - [ ] My commits follow Conventional Commits format
    - [ ] My commits do not include `Co-Authored-By` trailers
    
    ## Automated Checks
    
    <!-- Record current target-required checks and observed statuses only. -->
    
    ## Notes for Reviewers
    
    <!-- Describe dependencies or pending actions where applicable. -->
    ```
    
    ---
    
    ## Automated Checks
    
    These workflows may run on a PR. Establish which are REQUIRED from current target branch rulesets/branch protection and run status before asserting merge readiness. CodeRabbit is optional unless required by target policy; unknown requiredness blocks a merge-ready claim:
    
    | Check | What It Verifies | How to Fix |
    |-------|-----------------|------------|
    | **Check PR Cognitive Load** | PR stays within 400 changed lines (`additions + deletions`) or has `size:exception` | Split the PR, or document the human-selected `size:exception` rationale and verify actor `MAINTAIN`/`ADMIN` plus a current direct human instruction for the exact target/action before its canonical workflow action |
    | **Check Issue Reference** | PR body contains a visible, well-formed base-repository `Closes/Fixes/Resolves #N` or `Refs #N` | Add one valid reference; malformed, cross-repository, and mixed closing/non-closing re
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/gentleman-programming-gentle-ai-skills-branch-pr.md

// REPO STATS

9.0k stars
366 open issues
Last commit: 3d ago