Gentleman-Programming/gentle-ai

Agent skills in the GitHub repository Gentleman-Programming/gentle-ai, each with its code score out of 100.

Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Organic-Driven Development, curated skills, MCP servers, personas, and optional bounded review. Open source, no agent lock-in.

Repository score

68 / 100 C

Skills

20

Verified

1

Average skill score

62

GitHub stars

8,818

License

MIT

Open Gentleman-Programming/gentle-ai on GitHub

20 skills in this repository

1. 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 st…

   Verified88A
2. issue-creation

   Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

   75B
3. work-unit-commits

   Plan commits as reviewable work units. Trigger: commit splitting, chained PRs, or keeping tests and docs with code.

   71B
4. skill-creator

   Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.

   70B
5. issue-root-resolution

   Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue cluste…

   65C
6. rdd-defect-workflow

   Trigger: fixing RDD defects (review authority, receipts/lineage, correction/recovery, delivery gate). Not for using or toggling RDD.

   65C
7. skill-registry

   Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.

   64C
8. cognitive-doc-design

   Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

   63C
9. chained-pr

   Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

   62C
10. go-testing

    Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

    62C
11. gentle-ai-chained-pr

    Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

    61C
12. skill-improver

    Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

    60C
13. branch-pr

    Trigger: creating, opening, or preparing PRs. Follow the destination repository's contribution policy.

    59C
14. gentle-ai-branch-pr

    Trigger: preparing branches or PRs for Gentleman-Programming/gentle-ai. Apply this repository's issue-first contribution policy.

    58C
15. judgment-day

    Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

    58C
16. hermes-ephemeral-delegation

    Trigger: a mapping need, parallel units, context backstop, high-risk verify, fresh review, or multi-step debug. Delegate via delegate_task for a named reason.

    57C
17. comment-writer

    Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

    56C
18. gentle-ai-bench

    Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves dr…

    54D
19. rdd-advisory-transport

    Trigger: reviewer transport, advisory transport, review adapter, lens prompt/schema, OpenCode reviewer plugin, Codex reviewer, ReviewProviderContract. Enforce the shared Go adviso…

    48D
20. systemic-issue-triage

    Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrin…

    47D

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.