Agent skill

Monitor PR

by doc-detective in doc-detective/doc-detective

Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads.

AGPL-3.0Auto-check passedTesting & QA

Install Monitor PR

skills CLI
$ npx skills add doc-detective/doc-detective --skill monitor-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install doc-detective/doc-detective monitor-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/doc-detective/doc-detective.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/monitor-pr .claude/skills/monitor-pr && rm -rf skills-src

Use ~/.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/

Facts

Skill name
monitor-pr
GitHub stars
135
Token cost
~155 tokens
SKILL.md length
67 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads.

  • Tasks that involve Failing and flaky tests
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Monitor PR is an agent skill from doc-detective/doc-detective. Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads. Complete task after 3 consecutive PR checks with no new comments and passing CI.

Its SKILL.md is about 160 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 Testing & QA, covering Failing and flaky tests. The repository describes itself as: Doc Detective is an open-source documentation testing framework that makes it easy to keep your docs accurate and up-to-date. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Failing and flaky tests

Example prompts

  • “/monitor-pr”

What it can do on your machine

Read from SKILL.md and the folder at commit 388a6bc. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Monitor PR loads about 155 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 67 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~155

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 doc-detective/doc-detective at commit 388a6bc, republished under its AGPL-3.0 licence (© doc-detective). 67 words, ~155 tokens.

Download SKILL.mdSave it as .claude/skills/monitor-pr/SKILL.md (or your agent's skills folder).
name
monitor-pr
description
Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads. Complete task after 3 consecutive PR checks with no new comments and passing CI.

Monitor the current PR for CI failures and comments using the gh CLI. For each comment, assess whether it should be acted upon. Act upon it if necessary, respond in the comment thread, then resolve that thread. You must have 3 consecutive PR checks 4 minutes apart with no new comments and passing CI to complete your task. You must resolve all comment threads you respond to.

© doc-detective, AGPL-3.0. 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 .claude/skills/monitor-pr of doc-detective/doc-detective.

Open the folder on GitHubat commit 388a6bc

Compare with similar skills

Monitor PR 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.

Monitor PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monitor PR this skilldoc-detective/doc-detective135—~155Automated safety check: PassAGPL-3.0
Swig Testswig/swig6.3k—~2.3kAutomated safety check: PassCustom licence
Triage CI FailureDataDog/datadog-agent3.8k—~2.3kAutomated safety check: PassApache-2.0
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Fix Ready PRsfastrepl/anarlog9.5k—~1.4kAutomated safety check: PassMIT
Trx Analysismicrosoft/vstest969—~1.8kAutomated safety check: PassMIT

Similar skills

  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Triage CI Failure

    DataDog/datadog-agent

    Official

    Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.

    3.8k GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Fix Ready PRs

    fastrepl/anarlog

    Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.

    9.5k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Trx Analysis

    microsoft/vstest

    Official

    Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.

    969 GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Wio

    workersio/skills

    Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.

    190 GitHub stars~5.8k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

Categories

Questions about Monitor PR

What does Monitor PR do?

Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads. Monitor PR is an agent skill from doc-detective/doc-detective. Monitor PR for CI failures and comments, act on comments if necessary, respond to comments, and resolve comment threads.

When should I use Monitor PR?

Monitor PR fits situations like: tasks that involve Failing and flaky tests.

How do I install Monitor PR in Claude Code?

Run `npx skills add doc-detective/doc-detective --skill monitor-pr -a claude-code`. Or copy the skill folder (.claude/skills/monitor-pr in doc-detective/doc-detective) into .claude/skills/monitor-pr in your project. Claude Code loads it when a task matches its description.

How do I install Monitor PR in Codex?

Run `npx skills add doc-detective/doc-detective --skill monitor-pr -a codex`. Or copy the skill folder (.claude/skills/monitor-pr in doc-detective/doc-detective) into .agents/skills/monitor-pr in your project. Codex loads it when a task matches its description.

Can I use Monitor PR 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 doc-detective/doc-detective --skill monitor-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitor-pr, .gemini/skills/monitor-pr, .github/skills/monitor-pr and .opencode/skills/monitor-pr in your project.

What does Monitor PR need to run?

SKILL.md names no scripts, command-line tools or credentials: Monitor PR is instructions for the agent only.

Does Monitor PR access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Monitor PR 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 Monitor PR use?

Monitor PR is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Monitor PR use?

About 155 tokens (SKILL.md is roughly 620 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 Monitor PR?

Skills that share tags, products or a category with Monitor PR: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monitor PR?

doc-detective (a GitHub organization) maintains it in doc-detective/doc-detective, which has 135 GitHub stars. The repository was last updated on October 2, 2026.

Source: doc-detective/doc-detective on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.