Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the contribution flow is in scope: opening an issue, drafting or editing a PR body, splitting a change into chained/stacked PRs, or auditing a PR before requesting review.
Passed 20 of 23 test cases with the skill, and 6 of 23 without it.
and 16 more in the full report
14 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to know which file defines the automated CI gate checks for PR references and label status in `Gentleman-Programming/gentle-ai`. Should I check `.github/workflows/pr-check.yml` or infer them from issue templates?
| Checked | Without skill | With skill |
|---|---|---|
| identifies .github/workflows/pr-check.yml as the source of truth for automated PR workflow gates | Passed | Passed |
| advises inspecting repository source files rather than inferring rules | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the active repo is Gentleman-Programming/gentle-ai and the contributor is an external collaborator (not the maintainer). Scope of the skill:
Do NOT load this skill for:
The skill assumes the contributor is working from wherever they push — a fork, a personal working repo, or anywhere they have write access. It deliberately does not assume a fork. Use it whether you push to ardelperal/gentle-ai, to a personal fork, or to a contributor org.
Before any target-host read, obtain explicit authorization for the remote destination (exact target), read operation and credential/session; never probe ambient credentials. Locally, before recommending any contribution action, inspect the relevant current source. The repo documents every constraint; pulling rules verbatim beats guessing.
| Source | What it tells you |
|---|---|
CONTRIBUTING.md | Issue-first workflow, label taxonomy, branch naming regex ^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)\/[a-z0-9._-]+$, Conventional Commits format, 400-line review budget |
.github/PULL_REQUEST_TEMPLATE.md | Required PR body sections (Linked Issue, PR Type, Summary, Changes, AI Assistance, Test Plan, Automated Checks, Contributor Checklist, Notes for Reviewers) |
.github/ISSUE_TEMPLATE | Current issue templates, forms, and routing policy |
| Discovered GitHub labels | Current availability only; inventory is not permission. Use the reviewed CONTRIBUTING.md catalog |
.github/workflows/pr-check.yml | Automated gates: Check Issue Reference, Check Issue Has status:approved, Check PR Has type:* Label, Check PR Cognitive Load |
skills/branch-pr/SKILL.md | Branch + PR creation mechanics |
skills/chained-pr/SKILL.md | Chained vs Stacked PR strategy mechanics |
internal/assets/skills/issue-creation/SKILL.md | Canonical issue discovery, drafting, privacy review, and publication authority |
skills/cognitive-doc-design/SKILL.md | Doc-writing principles |
skills/comment-writer/SKILL.md | Tone for comment replies |
These files evolve. Re-read them at the start of every contribution.
test cases passed, vs 6 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.