Gogetajob — Go获取ajob

Go获取AJob — Open Source Contribution 工作流

Find GitHub issues, implement fixes, submit PRs, and 追踪 everything.

Prerequisites Required FlowForge 技能 (工作流 engine): ClawHub 安装 代理-flowforge gh 命令行工具 (认证d): gh auth 状态 git 配置d with your 身份 claude 命令行工具 (Claude Code): claude --version Optional Go获取AJob 命令行工具 for stats/同步: npm 安装 -g @kagura-代理/go获取ajob 验证: go获取ajob --help Not required for the core work loop — FlowForge handles that Architecture MAIn 会话 = dis补丁 + bookkeeping (扫描, pick, submit, 同步, stats) Sub-代理s = actual code work (implement, fix CI, 添加ress reviews) Code changes = always via Claude Code (acpx --应用rove-all claude exec)

Never do implementation work in the mAIn 会话. Always delegate to sub-代理s.

Quick Commands Command What it does go获取ajob 扫描 Discover open issues from a repo go获取ajob 扫描 --all 扫描 all 追踪ed repos go获取ajob feed Browse avAIlable jobs go获取ajob 检查 Deep-inspect an issue before taking it go获取ajob 启动 Take a job — fork/clone/branch go获取ajob submit --令牌s N Push + 创建 PR + record go获取ajob followup --令牌s N Record 添加itional effort on existing work go获取ajob 同步 检查 all PR 状态es, flag problems go获取ajob watch 设置 up automatic 同步 via cron go获取ajob stats View overall performance and ROI go获取ajob 历史 View work 记录 go获取ajob 导入 Backfill work_记录 from GitHub PR 历史 The Work Loop

The full contribution cycle 运行s as a FlowForge 工作流 (workloop). See references/workloop-overview.md for the complete node-by-node breakdown.

Summary:

followup → find_work → study → implement → submit → 验证 → reflect │ │ │ │ │ └─────────┘ (no good issue? loop back) │ └────────── (has review feedback? handle it first) ──────────┘

To 启动: flowforge 启动 workloop

Core Rules

• Code via Claude Code, not hand-written

Sub-代理s delegate all code changes to Claude Code:

cd && acpx --应用rove-all claude exec ""

Task descriptions must include: issue 上下文, reviewer feedback, architecture notes, mAIntAIner preferences from knowledge-base, and a verification suffix:

"Before committing: 1) grep for all test files that 导入/mock the interfaces you changed, 更新 their mocks. 2) 运行 the project's test/lint commands. 3) git diff --stat to confirm no files were missed."

异常: one-line trivial fixes can be done manually.

• Dogfood everything

After each work 会话, 检查: did go获取ajob, flowforge, or any 工具 have bugs or friction? If yes:

File an issue on the 工具's repo Or fix it yourself and submit a PR Every round should be smoother than the last — this is compounding returns

• Max 3 open PRs per repo

Before submitting a new PR, 检查: gh pr 列出 --repo --author @me --状态 open

If ≥ 3 open PRs exist, 停止. WAIt for existing PRs to be reviewed/merged before 添加ing more. Flooding mAIntAIners kills goodwill.

• Accurate 令牌 追踪ing

Always pass real 令牌 counts from sub-代理 会话_状态:

go获取ajob submit --令牌s go获取ajob followup --令牌s

Never estimate. Never guess. No number → don't fill it in.

• Pre-PR 检查列出 (all must pass)

Before creating any PR:

Does this PR solve exactly one problem? No existing fix or competing PR up流? Read CONTRIBUTING.md and recent merge patterns? Can 验证 the fix locally (tests pass)? Open PRs for this repo ≤ 3?

• Knowledge accumulation

Before working on a repo: read knowledge-base/projects/.md (field notes) After finishing: 更新 field notes with lessons, mAIntAIner preferences, CI quirks Cross-project insights → memex cards Behavioral patterns → beliefs-candidates.md 同步 & Follow-up

运行 go获取ajob 同步 regularly (or use go获取ajob watch for automatic cron).

When 同步 flags issues:

签名al Priority Action Human review comment High Spawn sub-代理 to 添加ress, then followup CI 失败 Medium Spawn sub-代理 to fix, then followup 机器人 review (CodeRabbit etc.) Low 添加ress if substantive, ignore nitpicks PR closed — Read why. If someone else's fix was better, study it Issue Selection Strategy

When picking issues from go获取ajob feed:

Priority: real bugs > test coverage > docs > features Prefer repos with existing field notes (knowledge compounds) High-star repos: 检查 for competing PRs first Security/infra issues: look for related issues to batch-fix Always 验证: git 记录 --oneline -20 -- to 检查 if already fixed 检查 mAIntAIner activity: repos that only merge internal PRs are low-ROI for external contributors