PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail.
Install Address Findings
$ npx skills add entireio/skills --skill address-findings -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install entireio/skills address-findings --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/address-findings .claude/skills/address-findings && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .claude/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/entireio/skills/tree/main/skills/address-findingsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add entireio/skills --skill address-findings -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install entireio/skills address-findings --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/address-findings .agents/skills/address-findings && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .agents/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add entireio/skills --skill address-findings -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install entireio/skills address-findings --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/address-findings .cursor/skills/address-findings && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .cursor/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/entireio/skills.git --path skills/address-findings--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add entireio/skills --skill address-findings -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install entireio/skills address-findings --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/address-findings .gemini/skills/address-findings && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .gemini/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install entireio/skills address-findingsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add entireio/skills --skill address-findings -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/address-findings .github/skills/address-findings && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .github/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add entireio/skills --skill address-findings -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install entireio/skills address-findings --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/entireio/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/address-findings .opencode/skills/address-findings && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "address-findings" agent skill from https://github.com/entireio/skills/tree/main/skills/address-findings into .opencode/skills/address-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-findings", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
address-findings- GitHub stars
- 223
- Token cost
- ~1.6k tokens
- SKILL.md length
- 868 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail.
- Works in 6 steps: Verify the CLI → Resolve the trail selector → Fetch open findings → …
- The user gives a trail URL
- SKILL.md covers When to use / not use, Response Format, Rules and Process, plus 1 more section
- Calls git
What it does
Address Findings is an agent skill from entireio/skills. Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the review skill.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review. The repository describes itself as: ✨ Cross-agent skills that help coding agents use Entire context from Checkpoints, sessions, and git history to search past work, explain code, and hand off sessions. The licence is MIT.
When your agent uses it
- The user gives a trail URL
- Number and asks to address
- Resolve its findings
- Review comments
Example prompts
- “/address-findings”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fe5266f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
entire.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Address Findings loads about 1.6k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 868 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from entireio/skills at commit fe5266f, republished under its MIT licence (© entireio). 868 words, ~1,565 tokens.
Download SKILL.mdSave it as
.claude/skills/address-findings/SKILL.md (or your agent's skills folder).- name
- address-findings
- description
- Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
- argument-hint
- <trail url or number>
Address Findings
Fix and resolve the open review findings on an Entire trail. A finding is a review comment posted to a trail on entire.io: it has a file/line location, a body, a severity, and sometimes a suggested unified-diff patch. This skill fetches the open findings, applies or hand-fixes each one in the current worktree, and marks it resolved on the trail.
When to use / not use
Use when the user points at a trail — a URL like
https://<host>/<forge>/<owner>/<repo>/trails/<number>/<slug>, or a bare trail
number or branch — and asks to address / fix / resolve its findings or
review comments.
Do not use this skill for:
- A code review of the current diff — that is the
reviewskill (read-only). - Creating new findings — use
entire trail finding add.
Response Format
Begin the first response to this skill invocation with the line:
Entire Address Findings:
followed by a blank line, then the content. Apply the header to the first response only. Omit it on error / early-exit responses (CLI missing, not authenticated, trail not found, branch mismatch, no open findings).
Rules
- Make the smallest correct change that addresses each finding. Do not expand scope.
- Only mark a finding resolved when you actually addressed it. If a finding is ambiguous or needs a human decision, leave it open and report it.
- Do not commit or push. Leave changes in the working tree for the user to review.
- Never weaken a test or assertion just to clear a finding.
Process
1. Verify the CLI
Run entire version. If the command is not found, stop and tell the user:
"The Entire CLI is required but not installed. Install it from
https://entire.io/docs/cli and try again."
2. Resolve the trail selector
- If the argument is a trail URL, take the number from the
/trails/<number>/path segment and use that number. - If it is a bare trail number, id, or branch name, use it as-is.
- If you cannot determine a trail, stop and ask the user for the trail URL or number.
Use this value as the <trail> selector for every command below. entire trail
accepts a trail number, id, or branch name interchangeably, so no number lookup
is needed — a branch name works directly.
3. Fetch open findings
entire trail finding list <trail> --json --status open- If the output reports that authentication is required, stop and tell the user:
"
entire trail finding listrequires authentication. Runentire loginand try again." - If the
trail findingsubcommand is unavailable, or the API reports the feature is not enabled, stop and tell the user that trail findings may not be enabled for this account or repository. Do not invent findings. - Parse the JSON. Each finding has an id, a severity, a status, a body, a location (file path + line range), and may include a suggested change (a unified diff).
- If there are no open findings, report "No open findings on this trail." and stop.
4. Branch guard (you must be on the trail's branch)
entire trail finding apply edits the local worktree, so you must be on the
trail's branch before changing files.
git rev-parse --abbrev-ref HEAD # current branch
entire trail list --json --status any -n 200 # locate the trail's branchFind the trail whose number or branch matches your selector and read its branch.
- If the trail's branch differs from the current branch, stop and tell the user:
"Trail
<trail>targets branch<trail-branch>, but you are on<current-branch>. Check it out first (entire trail checkout <trail>) and re-run." Do not edit files. - If you cannot find the trail in the list (e.g. pagination), do not hard-fail: warn that you could not verify the branch, and ask the user to confirm they are on the trail's branch before you continue.
Show full SKILL.md (302 more words)Show less
5. Address each finding
Process findings highest severity first (high → medium → low). For each:
If it has a suggested unified-diff change, dry-run it first:
bash entire trail finding apply <trail> <finding-id> --checkIf it applies cleanly, apply and resolve in one step:
bash entire trail finding apply <trail> <finding-id> --resolveOtherwise (no patch, the patch conflicts, or the fix needs reasoning): read the finding body, open the file at its location, and make the smallest correct edit that addresses it. If a fast, relevant local check exists for the touched code (a build or a focused test), run it. Then resolve:
bash entire trail finding resolve <trail> <finding-id> -m "<one line: what you changed>"If you cannot confidently address it (ambiguous, needs a product/design decision, or out of scope): leave it open, do not resolve it, and record it for the report.
6. Report
Summarize:
- Resolved via suggested patch — list finding ids and files.
- Resolved via manual edit — list finding ids, files, and a one-line of what changed.
- Left open for your decision — list finding ids and why.
- Any errors encountered.
Remind the user the changes are uncommitted and ready for review.
Failure modes
- CLI not installed → install message (step 1).
- Not authenticated → "
entire trail finding listrequires authentication. Runentire loginand try again." - Trail findings not enabled / API error → tell the user the feature may be unavailable; do not fabricate findings.
- Trail not found → tell the user to check the URL or number; suggest
entire trail list --status any. - Wrong branch → stop with the checkout instruction (step 4).
- Patch does not apply → fall back to a manual edit; if you cannot fix it confidently, leave the finding open and report it.
- Not a git repository → stop and tell the user to run from inside the trail's repo.
© entireio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/address-findings of entireio/skills.
Open the folder on GitHubat commit fe5266f
Compare with similar skills
Address Findings next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Address Findings this skillentireio/skills | 223 | — | ~1.6k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Backend Code Reviewlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Notes | MIT | |
| Mole Bug Patternstw93/Mole | 70k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Backend Code Reviewlanggenius/dify | 158k | — | ~676 | Automated safety check: Pass | Custom licence |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from entireio/skills
All 12 skills in this repoReview
entireio/skills
Review code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff.
Recall
entireio/skills
A skill your agent uses when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook.
Replay
entireio/skills
A skill your agent uses when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions.
Search
entireio/skills
A skill your agent uses when the user asks to research, investigate, look into, dig into, or search for anything — a topic, feature, bug, decision, or "what do we know about X".
Session Crosslink
entireio/skills
A skill your agent uses when an agent session ran outside the repo whose commits should record it — e.g.
Session To Skill
entireio/skills
A skill your agent uses when the user wants to turn one or more Entire-tracked sessions, checkpoints, or repeated agent workflows into a reusable agent skill.
Related
Categories
Questions about Address Findings
What does Address Findings do?
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Address Findings is an agent skill from entireio/skills. Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail.
When should I use Address Findings?
Address Findings fits situations like: the user gives a trail URL; number and asks to address; resolve its findings; review comments.
How do I install Address Findings in Claude Code?
Run `npx skills add entireio/skills --skill address-findings -a claude-code`. Or copy the skill folder (skills/address-findings in entireio/skills) into .claude/skills/address-findings in your project. Claude Code loads it when a task matches its description.
How do I install Address Findings in Codex?
Run `npx skills add entireio/skills --skill address-findings -a codex`. Or copy the skill folder (skills/address-findings in entireio/skills) into .agents/skills/address-findings in your project. Codex loads it when a task matches its description.
Can I use Address Findings in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add entireio/skills --skill address-findings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/address-findings, .gemini/skills/address-findings, .github/skills/address-findings and .opencode/skills/address-findings in your project.
What does Address Findings need to run?
Going by SKILL.md and its folder, Address Findings needs the command-line tools its instructions call (git).
Does Address Findings access the network?
SKILL.md names 1 domain. As links in the text: entire.io. This is read from the text; nothing was executed.
Is Address Findings safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Address Findings use?
Address Findings is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Address Findings use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Address Findings?
Skills that share tags, products or a category with Address Findings: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 155k stars) and Mole Bug Patterns (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Address Findings?
entireio (a GitHub organization) maintains it in entireio/skills, which has 223 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 29, 2026.
Source: entireio/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.