agentleFS
Sign inStart free
oocxoocx/tfplan2md/.claude/skills/watch-uat-github-pr/SKILL.md

watch-uat-github-pr

Skill174 starsChanged 2 months agoMITView on GitHub

Watch a GitHub UAT PR for maintainer feedback or approval by polling comments until approved/passed.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use scripts/uat-watch-github.sh (single stable command).

    line 26
  2. Very specific:

    Treat any detected approval (approved|passed|accept|lgtm) as UAT passed.

    line 27
  3. Distinctive:

    Stop watching and report when the PR is closed.

    line 28
  4. Very specific:

    Run many ad-hoc gh commands.

    line 33
  5. Distinctive:

    Stop and report if the PR is closed/merged

    line 43
  6. Very specific:

    Treat any detected approval (approved|passed|accept|lgtm) as UAT passed

    line 44

≈ “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

Watch UAT PR (GitHub)

Purpose

UAT comment polling is historically brittle. This skill standardizes the watch loop so the agent can reliably wait for Maintainer feedback/approval.

Preferred: use GitHub chat tools to poll PR state + comments (avoids terminal output/pager issues). Fallback: use the stable wrapper command.

Fallback path uses the repo wrapper script scripts/uat-watch-github.sh, which repeatedly calls scripts/uat-github.sh poll until:

  • approval keywords are detected, or
  • the PR is closed/merged, or
  • a timeout is reached.

Hard Rules

Must

  • Use scripts/uat-watch-github.sh (single stable command).
  • Treat any detected approval (approved|passed|accept|lgtm) as UAT passed.
  • Stop watching and report when the PR is closed.

Must Not

  • Spam comments or post follow-ups while waiting.
  • Run many ad-hoc gh commands; prefer the wrapper.

Actions

Preferred: Poll using GitHub chat tools

Repeatedly:

  • Fetch PR details (state)
  • Fetch PR conversation comments
  • Stop and report if the PR is closed/merged
  • Treat any detected approval (approved|passed|accept|lgtm) as UAT passed

Fallback: One-command wrapper

1. Watch the PR

scripts/uat-watch-github.sh <pr-number>

2. Optional: Tune polling interval / timeout

scripts/uat-watch-github.sh <pr-number> --interval-seconds 60 --timeout-seconds 3600

Output

  • Exit code 0: approval detected or PR closed (treat as pass)
  • Exit code 1: timed out (treat as incomplete; ask Maintainer)

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.

Check your setup, free