Agent skill for clawsweeper-status
Loading actions...
STRIDE threat modeling) and code architecture
param2: value2)'
capitalization
Run the bundled status script first:
/Users/steipete/Projects/agent-scripts/skills/clawsweeper-status/scripts/clawsweeper-status.sh
Useful options:
# Last 10 hours for the default target repo, openclaw/openclaw
/Users/steipete/Projects/agent-scripts/skills/clawsweeper-status/scripts/clawsweeper-status.sh --hours 10
# A different target repo
/Users/steipete/Projects/agent-scripts/skills/clawsweeper-status/scripts/clawsweeper-status.sh --repo openclaw/clawhub
# More rows per activity section
/Users/steipete/Projects/agent-scripts/skills/clawsweeper-status/scripts/clawsweeper-status.sh --limit 15
Report these sections concisely:
Workers: active workflow count, queued/waiting count, active Codex job estimate, and active workflow groups.Recently merged: merged PR URLs plus one-line titles.Recently reviewed: ClawSweeper/Codex review comment URLs plus one-line comment summary.Recently commented: other recent ClawSweeper comment URLs plus one-line comment summary.Recently closed: closed issue/PR URLs plus one-line titles.If the script returns no rows for a section, say none found in window.
Prefer the script because it uses bounded API calls:
openclaw/clawsweeper;Do not browse the web for these checks. Use gh directly.
gh run list output cautiously; prefer gh api repos/openclaw/clawsweeper/actions/runs?... and per-run jobs when the numbers disagree.