ClawOSS

Discover FRESH issues in WELL-MAINTAINED repos (200+ stars). Merge-optimized: 60% easy wins (docs, typos, tests) + 40% bug fixes. Target agentic AI repos by CRITERIA (topic:llm/agent/rag + stars:>200). Verify repo health before queuing.

Orchestrator-level PR follow-up detection and delegation: scan open PRs for new review comments, classify feedback type, write context files to subagent-inputs, delegate to oss-pr-review-handler sub-agents. Does NOT implement changes directly.

Sub-agent skill for handling PR review feedback: clone repo, checkout PR branch, read all review comments (inline + general), implement requested changes, push updates, respond to reviewers via gh CLI, cleanup workspace. Spawned 1-per-PR by the orchestrator.

Submit a contribution PR (bug fix, docs fix, typo fix, or test addition) to an open-source repo: verify it's a valid contribution, push branch to fork, create PR with gh CLI, use repo's PR template, log submission, report to dashboard.

Triage GitHub issues: confirm contribution type (bug/docs/typo/test), assess feasibility, check repo health (merge velocity, review rate). Merge-optimized scoring: +5 docs/typo, +3 tests, +5 fast merge repos. REJECT issues in unhealthy repos.

Analyze repo health and conventions BEFORE queuing any issue. MANDATORY health gate: stars >=200, last commit <2wk, merge time <14d, review rate >50%, open PRs <50. Use /Users/kevinlin/clawOSS/scripts/repo-health-check.sh for automation.

Final safety gate before PR submission: contribution type verification (bug/docs/typo/test), budget check, diff size 25-100 LOC target (HARD MAX 200), no secrets, branch naming, dedup check, independent review. Abort if any check fails.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Manage context window: monitor usage, flush state to memory at 80% capacity, write work-in-progress summary, trigger compaction, re-read memory after compaction.

Implement an OSS contribution (bug fix, docs fix, typo fix, or test addition) using deep-comprehension workflow. For bugs: trace root cause, reproduce-first, comprehensive fix. For docs/typos: verify correctness. For tests: meaningful coverage. REJECT feature requests.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Pre-submission self-review for contributions (bug fixes, docs fixes, typo fixes, test additions): run git diff, check all 8 quality gates (contribution type gate, scope, code quality, tests, security, anti-slop, git hygiene, PR template). ABANDON if not a valid contribution.

Report metrics and events to ClawOSS dashboard API via curl.