Run any Skill in Manus with one click

patrol

Stars0

Forks0

UpdatedApril 17, 2026 at 00:19

Scan and auto-fix open GitHub issues across a target repository using the StatsClaw 9-agent workflow. Use this skill whenever the user asks to "patrol issues", "triage and fix open issues", "sweep the issue tracker", "resolve bugs in <repo>", or invokes $patrol explicitly. The skill runs Workflow 4 (Issue Patrol) — it lists open issues, triages them, dispatches the planner → builder → tester → scriber → reviewer → shipper chain for each in-scope issue, opens PRs, and posts reply comments. Accepts arguments of the form `<owner/repo> [base-branch]` or a GitHub URL.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

statsclaw

statsclaw/statsclaw-codex

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	patrol
description	Scan and auto-fix open GitHub issues across a target repository using the StatsClaw 9-agent workflow. Use this skill whenever the user asks to "patrol issues", "triage and fix open issues", "sweep the issue tracker", "resolve bugs in <repo>", or invokes $patrol explicitly. The skill runs Workflow 4 (Issue Patrol) — it lists open issues, triages them, dispatches the planner → builder → tester → scriber → reviewer → shipper chain for each in-scope issue, opens PRs, and posts reply comments. Accepts arguments of the form `<owner/repo> [base-branch]` or a GitHub URL.
metadata	{"short-description":"Issue patrol — scan, triage, auto-fix, PR, reply"}

Skill: Patrol — Auto-triage and fix open GitHub issues

You are the StatsClaw leader. The user has triggered $patrol (or described a patrol-shaped task in natural language).

Run Workflow 4 (Issue Patrol) from skills/statsclaw-protocol/SKILL.md. The authoritative procedure lives in skills/issue-patrol/SKILL.md — load that file and follow it exactly.

Quick summary (full details in skills/issue-patrol/SKILL.md)

Parse arguments: resolve <repo> to owner/repo. Accept GitHub URLs, owner/name, or bare repo name if unambiguous from workspace context.
Run the standard session-start gates (detect mode, acquire workspace, verify credentials). See skills/credential-setup/SKILL.md.
Create a patrol run directory under ${STATSCLAW_CODEX_DATA}/workspace/<repo>/runs/PATROL-<timestamp>/.
Scan phase — gh issue list --repo owner/repo --state open --limit 50. Classify each into triage buckets (bug / feature / question / duplicate / out-of-scope) and write patrol-triage.md.
Fix loop — for each in-scope issue:
- Create issue-<number>/ sub-run directory.
- Dispatch planner → builder → tester → scriber → reviewer → shipper via scripts/dispatch.sh.
- Shipper pushes a branch, opens a PR that references the issue (Fixes #N), and posts a comment on the issue linking the PR.
Report phase — write patrol-report.md summarizing issues touched, PRs opened, issues skipped and why.

If the user supplies a [base-branch], all PRs target that branch; otherwise default to the repo's default branch.

Patrol runs autonomously — no per-issue user confirmation. The only pause is HOLD when planner needs clarification.

Before you start, confirm the interpreted arguments (repo + base-branch) back to the user with a numbered-options question if anything is ambiguous.

More from this repository

same repository

attribution

statsclaw/statsclaw-codex

[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Commit authorship policy: shipper and every other agent must NOT append any Co-authored-by trailer, tooling footer, or bot identity to commit messages. The user is the sole author of every commit produced by the framework.

2026-04-170

brain-sync

statsclaw/statsclaw-codex

[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Knowledge-sharing lifecycle: Opt-In → Acquire → Read → Extract → Consent → Upload. Drives when and how the distiller is dispatched, how brain-contributions.md is surfaced to the user, and how approved entries are PR-ed to statsclaw/brain-seedbank.

2026-04-170

statsclaw-protocol

statsclaw/statsclaw-codex

[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Core orchestration protocol for the StatsClaw 9-agent framework. Defines every gate, state transition, precondition, must-not rule, workflow catalog, and signal-handling policy that the leader enforces.

2026-04-170

brain

statsclaw/statsclaw-codex

Enable, disable, or inspect the StatsClaw shared brain — the cross-user knowledge system that lets agents read curated statistical knowledge and optionally contribute back. Use this skill when the user says "turn on brain", "enable brain mode", "turn off brain", "check brain status", "brain on", "brain off", or invokes $brain with on/off/status. Saves the setting to context.md and clones the brain repos if enabling. Full contribution lifecycle lives in skills/brain-sync.

2026-04-170

contribute

statsclaw/statsclaw-codex

Extract reusable knowledge from the current session, privacy-scrub it, and (with explicit user consent) submit it to the shared StatsClaw brain-seedbank as a pull request. Use this skill when the user says "contribute", "share what I learned", "submit lessons", "add to brain", "contribute knowledge", or invokes $contribute. Bypasses the automatic frequency heuristic but applies the same quality gate and mandatory user-consent step — nothing is uploaded without explicit approval.

2026-04-170

credential-setup

statsclaw/statsclaw-codex

[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] GitHub credential detection and verification. Establishes whether gh CLI, SSH key, $GITHUB_TOKEN, or a credential helper is available before any network-touching work runs.

2026-04-170

name	patrol
description	Scan and auto-fix open GitHub issues across a target repository using the StatsClaw 9-agent workflow. Use this skill whenever the user asks to "patrol issues", "triage and fix open issues", "sweep the issue tracker", "resolve bugs in <repo>", or invokes $patrol explicitly. The skill runs Workflow 4 (Issue Patrol) — it lists open issues, triages them, dispatches the planner → builder → tester → scriber → reviewer → shipper chain for each in-scope issue, opens PRs, and posts reply comments. Accepts arguments of the form `<owner/repo> [base-branch]` or a GitHub URL.
metadata	{"short-description":"Issue patrol — scan, triage, auto-fix, PR, reply"}

Skill: Patrol — Auto-triage and fix open GitHub issues

You are the StatsClaw leader. The user has triggered $patrol (or described a patrol-shaped task in natural language).

Run Workflow 4 (Issue Patrol) from skills/statsclaw-protocol/SKILL.md. The authoritative procedure lives in skills/issue-patrol/SKILL.md — load that file and follow it exactly.

Quick summary (full details in skills/issue-patrol/SKILL.md)

Parse arguments: resolve <repo> to owner/repo. Accept GitHub URLs, owner/name, or bare repo name if unambiguous from workspace context.
Run the standard session-start gates (detect mode, acquire workspace, verify credentials). See skills/credential-setup/SKILL.md.
Create a patrol run directory under ${STATSCLAW_CODEX_DATA}/workspace/<repo>/runs/PATROL-<timestamp>/.
Scan phase — gh issue list --repo owner/repo --state open --limit 50. Classify each into triage buckets (bug / feature / question / duplicate / out-of-scope) and write patrol-triage.md.
Fix loop — for each in-scope issue:
- Create issue-<number>/ sub-run directory.
- Dispatch planner → builder → tester → scriber → reviewer → shipper via scripts/dispatch.sh.
- Shipper pushes a branch, opens a PR that references the issue (Fixes #N), and posts a comment on the issue linking the PR.
Report phase — write patrol-report.md summarizing issues touched, PRs opened, issues skipped and why.

If the user supplies a [base-branch], all PRs target that branch; otherwise default to the repo's default branch.

Patrol runs autonomously — no per-issue user confirmation. The only pause is HOLD when planner needs clarification.

Before you start, confirm the interpreted arguments (repo + base-branch) back to the user with a numbered-options question if anything is ambiguous.