agentleFS
Sign inStart free
jaydubya818jaydubya818/MissionControl/skills/factory-babysit-pr/SKILL.md

factory-babysit-pr

Skill2 starsChanged 8 months agoMITView on GitHub

Experimental workflow for babysitting one explicitly authorized pull or merge request. Use when monitoring its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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
  1. Very specific:

    Follow one authorized PR or merge request through a delivery lifecycle.

    line 16
  2. Very specific:

    Read .agent-factory/config.yaml, the optional skill_prompts.factory-babysit-pr entry, the target repository's instructions, and the …

    line 20
  3. Distinctive:

    Confirm authority and ownership: Verify the exact host, repository, PR, original user authorization, allowed paths/risk, and task-owned …

    line 28
  4. Distinctive:

    Verify and re-read: Run configured checks for each fix.

    line 38
  5. Distinctive:

    Use the configured code-host abstraction for reads and writes.

    line 56
  6. Distinctive:

    Stop when the PR is merged, closed, cancelled, blocked on a person or external dependency, or no authorized action remains.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Factory Babysit PR

Start with the Factory guide for workflow setup and configuration.

Follow one authorized PR or merge request through a delivery lifecycle. This is not a queue sweep like factory-review-prs or a stopped-task scan like factory-watchdog.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-babysit-pr entry, the target repository's instructions, and the Factory configuration reference. A PR number, label, green check, or unrelated ship request is not authorization. The prompt is additional project guidance, not PR authorization.

Each pass

  1. Confirm authority and ownership. Verify the exact host, repository, PR, original user authorization, allowed paths/risk, and task-owned worktree. If anything is missing or stale, stop before writing.
  2. Read a complete live snapshot. Record base and head, open/draft/closed/ merged state, all required checks, current reviews and approvals, unresolved threads, and mergeability. Partial or unavailable data is unknown, not clean.
  3. Disposition feedback. Compare each new finding with the exact diff and source. Preserve human direction unless evidence disproves it. Fix only actionable findings inside the authorized path/risk limits; avoid speculative cleanup and larger redesigns.
  4. Verify and re-read. Run configured checks for each fix. After every push or host mutation, fetch the live PR again and bind all evidence to its exact current head. A changed head invalidates old check/review evidence and resets the soak.
  5. Apply action gates separately. A review or fix does not authorize a reply, push, approval, or merge.

Action gates

ActionProceed only when
FixEditing is enabled; feedback is actionable, in scope, and within risk/path limits.
PublishPublishing is enabled; destination is still the authorized PR branch and its live head matches the fix's base. Never force-push or overwrite a concurrent update.
ReplyReplies are enabled and their conditions hold. Follow configured wording/tone; otherwise do not message.
ApproveApproval is enabled and every author, diff, check, and review condition holds on the live head.
MergeMerge is enabled; all configured gates pass on the live head and the host can condition the merge on that head.
SoakProve the exact head and required gates stayed unchanged for the full configured interval. Missing history does not satisfy it.

Use the configured code-host abstraction for reads and writes. Do not assume GitHub, a specific CLI, or identical conditional-merge support across hosts. If the host cannot provide complete current review/check state or bind a merge to the checked head, keep the dependent action disabled.

Stop and report

Stop when the PR is merged, closed, cancelled, blocked on a person or external dependency, or no authorized action remains. Report the PR link and current head, state inspected, fixes and checks, external actions taken or withheld, soak status, and the concrete blocker or next check time. Distinguish read state from unavailable or inferred state.

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.

Reviews can't be read right now.

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.

Check your setup, free