agentleFS
Beskars-CodeBeskars-Code/Skills/skills/takeover-pr/SKILL.md

takeover-pr

Skill0 starsChanged 5 days agoMITView on GitHub

Use only when the user explicitly asks to assess, revive, or take over an old PR. Checks whether it still fits current code before recommending continue, rework, or closure; implements and publishes only within authorized scope.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every run applies code quality, code structure, and Plain language.

    line 9
  2. Distinctive:

    Before a decision, use Asking the user.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Take over a PR

Every run applies code quality, code structure, and Plain language. Before a decision, use Asking the user. Carry the updated intent in the existing execution context.

  1. Read intent-aware takeover, execution preflight.
  2. Inspect the source PR/history and current target under the shared takeover contract. Preserve authorship, unrelated work and settled user decisions.
  3. Present the evidenced continue/rework/closure recommendation and authority boundary. Stop if the request was assessment only or a material decision blocks continuation; follow asking rules.
  4. For authorized work, hand the updated intent and pinned scope to the selected build skill via the Skills table in AGENTS.md. Reuse its readiness, checks, review and shipping contracts rather than copying their orchestration.
  5. Report the resulting diff, source credit, checks and remaining blockers. Watch only if requested, with the existing parent as sole owner under PR lifecycle.

A simple request to sync main follows Git sync only, without this assessment.

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.