monitor-ci

A command that watches the automated checks for a GitHub pull request. These checks commonly build the project, run tests, or inspect code before changes are merged.

In plain words
What is it for?
Use it after opening or updating a pull request to wait for all checks to finish, inspect failure logs, and suggest or make fixes.
Why use it?
It removes the need to repeatedly refresh the pull request and helps identify why a check failed.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/liam-hq/liam/monitor-ci
Clone the repo
git clone --depth 1 https://github.com/liam-hq/liam

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00364
Opus 5 $0.00000 $0.00182
Sonnet 5 $0.00000 $0.00073
Haiku 4.5 $0.00000 $0.00036

Measured 3d ago against content hash 8947e612b53f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

monitor-ci scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/monitor-ci.md · 56 lines

What it actually says

Monitor CI Checks

Monitors pull request CI checks until they are resolved (pass or fail).

Usage

When asked to monitor CI checks, Claude will:

  1. Run gh pr checks --watch to continuously monitor the status
  2. Wait until all checks are completed
  3. Report the final status of all checks
  4. If checks fail, analyze the failure logs and suggest fixes

Command

# Monitor PR checks in watch mode
gh pr checks --watch

# Alternative: Check status once
gh pr checks

# View specific check details if needed
gh pr checks --verbose

Workflow

  1. Start Monitoring: Run gh pr checks --watch immediately after PR creation or when requested
  2. Track Progress: The command will show real-time updates of all CI checks
  3. Completion: Wait until all checks show as either ✓ (passed) or X (failed)
  4. Action on Failure:
    • If any checks fail, use gh pr checks --verbose to get detailed logs
    • Analyze the failure and suggest or implement fixes
    • After fixes, push changes and monitor again

Example Output

Refreshing checks status every 10 seconds. Press Ctrl+C to quit.

NAME                    STATUS      CONCLUSION
Build                   completed   success     ✓
Lint                    completed   success     ✓
Test                    completed   failure     X
Type Check              in_progress -           ◐

Some checks were not successful

Important Notes

  • The --watch flag refreshes every 10 seconds
  • Press Ctrl+C to stop monitoring
  • Always wait for all checks to complete before proceeding
  • If checks fail, investigate and fix issues before merging
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 56 lines · 0 tokens per session scan A 8947e612b53f

Subscribe to this mod's changes

monitor-ci is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 364 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.