← ClaudeAtlas

gh-contribution-plannerlisted

Daily GitHub contribution planner — analyzes the gh-logged-in user's non-archived repos (owned + forks) and recent contributions, produces a prioritized plan, halts for approval, then dispatches parallel sub-agents to execute approved items via existing PR/CI/review skills.
ulises-jeremias/agent-toolkit · ★ 14 · AI & Automation · score 79
Install: claude install-skill ulises-jeremias/agent-toolkit
# GitHub Contribution Planner Discover what to work on across **your** GitHub footprint, propose a prioritized daily plan, and — on approval — fan out parallel sub-agents to open draft PRs. The skill infers the current user from the authenticated `gh` CLI, so no manual configuration is required. ## When to use - "Plan my GitHub contributions for today" / "what should I work on across my repos" / "give me a daily contribution plan". - You want to maintain your own repositories and forks without manually scanning each one. - You want to find low-friction openings (good first issues, stale PRs, outdated forks) in projects you have already contributed to. Do **not** use this skill to operate on a specific PR you already picked — use `gh-fix-ci`, `gh-address-comments`, or `github-cli-workflow` directly. ## Prerequisites - `gh` installed and authenticated (`gh auth status` exits 0). Scopes typically required: `repo`, `read:org`. `doctor` reports this under Integrations. - `python3` for the bundled analyzer. - Network access to `api.github.com` (or the host configured via `GH_HOST`). - A host that supports parallel sub-agent dispatch (Claude Code's `Task` tool, OpenCode's subagent fan-out, etc.). Hosts without that primitive fall back to sequential execution. ## Workflow 1. **Verify auth.** Run `gh auth status`. If unauthenticated, ask the user to run `gh auth login` and stop. Do not prompt for tokens. 2. **Resolve the current user.** `gh api user --jq .log