agentleFS
skillberry-aiskillberry-ai/cap-evolve/.claude/skills/open-pr/SKILL.md

open-pr

Skill70 starsChanged 7 days agoApache-2.0View on GitHub

Entry point for an AI agent doing development work in cap-evolve - branch off main, commit as the right identity, pick the right testing/review track for the change (code, dashboard, or docs-only), and open the PR with the house checklist filled in. Use whenever asked to implement a change, fix a bug, or open a PR in this repo.

  • Commits and pushes

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-change, commit-push and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • thlaureSkill

    review-change

    Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

    Also in 4 projects that use this

  • DataCoveySkill

    commit-push

    Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.

    Also in 3 projects that use this

  • Codagent-AISkill

    implement-change

    Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

    Also in 3 projects that use this

  • saffron-healthSkill

    address-review

    Address PR review comments systematically. Use when responding to code review feedback on a pull request.

    Also in 3 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 10 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Commit and open the PR as the user's own configured git identity — never as an AI tool's identity, and never add a tool co-author trailer, …

    line 29
  2. Very specific:

    If you are unsure which track a change is, read the diff's file list: anything under dashboard/frontend/src/ with no …

    line 46
  3. Very specific:

    Follow CONTRIBUTING.md's house rules (honesty lives only in core/cap_evolve, skills stay host-agnostic, zero runtime deps in core, a test …

    line 53
  4. Distinctive:

    After the last review round reports both verdicts, hand back to the user.

    line 87

“Common” is measured: kept by at least 6 in 10 of the 66 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Open a PR

The single entry point other skills assume you went through: testing, review-cycles, dashboard-change, docs-change. Read this first for any development task in cap-evolve, then branch into the skill(s) your change's track needs.

1. Branch

Work in a worktree, not the checkout the user is sitting in (see superpowers:using-git-worktrees if available, else git worktree add), branched from a fresh origin/main:

git fetch origin main
git worktree add -b <type>/<short-slug> ../wt-<slug> origin/main

Pick <type> the way this repo's history does: feat, fix, refactor, chore, docs, test.

2. Identity

Commit and open the PR as the user's own configured git identity — never as an AI tool's identity, and never add a tool co-author trailer, unless the user's own instructions (a CLAUDE.md, a memory, or something said this session) say otherwise for this session. Check git config user.name/user.email match what the user expects before your first commit.

3. Classify the change — pick the track

TrackWhat it isWhat happens before review
Codecore/cap_evolve, skills/*/*/scripts, dashboard/backend/capevolve_dashboard, CI, adapters, anything with logicRun the testing skill: unit tier always, end-to-end real run(s) when the change plausibly affects a real run
Dashboarddashboard/frontend/src/** (components, routes, styles)Run dashboard-change: build, screenshot before/after, attach to the PR — no real end-to-end optimization run needed
Docs-only*.md, docs/**, site/** prose, SKILL.md body text, comments-only diffsRun docs-change: link check only, no real run

A PR can touch more than one track (e.g. a feature with code + docs) — run every track's prep, then one shared review-cycles pass over the whole diff.

If you are unsure which track a change is, read the diff's file list: anything under dashboard/frontend/src/ with no core//skills//dashboard/backend/ changes is dashboard-only; anything that is 100% .md/doc-comment is docs-only; everything else is code.

4. Commit

Follow CONTRIBUTING.md's house rules (honesty lives only in core/cap_evolve, skills stay host-agnostic, zero runtime deps in core, a test for any core/skills/dashboard code change). Use git commit -s if the repo's commits are signed off (check git log -5 for Signed-off-by trailers).

5. Open the PR

gh pr create --title "<type>: <summary>" --body "$(cat <<'EOF'
## What & why
...

## Checklist
- [ ] python -m pytest core/tests -q passes
- [ ] python skills/_registry/build_manifest.py skills is clean
- [ ] Any new/changed skill's scripts/check.py is green
- [ ] Honesty invariants untouched (gate on val, test sealed) — or explained
- [ ] Docs updated (README/skill SKILL.md) if behavior changed
EOF
)"

This is .github/PULL_REQUEST_TEMPLATE.md verbatim — fill in the checkboxes with what you actually ran, don't just check them.

6. Test and review

Go run the track(s) from step 3, then review-cycles for 3 rounds. Do not open the PR for review before the relevant test evidence (a real run's link/score, or screenshots, or the link-check result) is either already in the PR description or about to be posted as the first comment — reviewers judge against that evidence.

7. Finish

After the last review round reports both verdicts, hand back to the user. Do not merge on your own unless explicitly asked to.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.