Skip to content
Diagnosis · Security

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is…

Testing what is locked and what isn’t

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
One command
Best in a coding tool, where its scripts can run.
Contains
Instructions + 2 scripts
Python.
Maintained
Last change 3 Oct 2026
On the repository’s main branch.

What it does

Objective Babysit a PR persistently until one of these terminal outcomes occurs:

When your AI uses it

Use when the user as

You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.

What it can touch

  • Includes 2 scripts

    Your AI can run these when the skill is used — on your computer in a coding tool (which asks first unless you have told it not to), or in the AI’s own sandbox in Claude and ChatGPT.

    How we know

    Found in the skill’s folder: scripts/gh_pr_watch.py, scripts/test_gh_pr_watch.py.

  • Uses terminal commands

    It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.

    How we know

    The SKILL.md contains shell code blocks.

  • No known risk pattern found

    Launch7’s automated check read all 6 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit c3a2e68 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to deonmenezes/mantishack: 2026-10-03 (2 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Partly. Upload it in Claude’s settings — the instructions work; the scripts need the full folder.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

This skill ships 2 scripts beside its instructions. The download here is the SKILL.md alone — enough for the instructions, not for the parts that run code. Use the command route, or take the full folder from the repository.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from deonmenezes

All from this publisher →
  • codex-bug

    Diagnose GitHub bug reports in openai/codex.

    deonmenezesContacts outside web addresses
  • codex-issue-digest

    Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows.

    deonmenezesIncludes 2 scripts
  • findings-spine

    Record and advance every vulnerability finding through the tool-owned mantis_findings service instead of tracking findings in prose

    deonmenezesInstructions only
  • mantis-pipeline

    The master Mantis playbook -- how to run an authorized vulnerability-discovery engagement end to end, which subagent owns each stage, which…

    deonmenezesInstructions only
  • openai-docs

    Provide authoritative, current guidance from OpenAI developer docs using the developers.openai.com MCP server.

    deonmenezesIncludes 2 scripts