auto-github-contributor

Automate end-to-end GitHub contributions by resolving issues and opening pull requests.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/pftom/auto-github-contributor --skill auto-github-contributor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-github-contributor
Source: https://github.com/pftom/auto-github-contributor/tree/main/skills/auto-github-contributor
Command: npx skills add https://github.com/pftom/auto-github-contributor --skill auto-github-contributor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, python3, rg, and includes scripts (resource) components.

What problem does it solve?

Developers often waste time locating suitable contributions and coordinating end-to-end workflow to create PRs for open-source projects. This Skill streamlines the process by surfacing quick-win issues and repo cleanups, then guiding a complete development loop until quality gates (lint, typecheck, tests) pass.

Core Features & Use Cases

  • Discover labeled issues (e.g., good first issue, help wanted, documentation) and repo quick-wins (typos, missing tests, i18n gaps, TODOs) in parallel.
  • Run a TDD-style development loop that iterates on tests, implementation, and refactoring until lint, typecheck, and tests are all green.
  • Open PRs via GitHub CLI (gh pr create) and return the PR URL for easy sharing and review.
  • Provide interactive prompts, safety rails, and provenance (SPEC.md/TODO.md) to ensure auditable changes.

Quick Start

Invoke the Claude Code slash command to scan a target repo, pick a task, and open a PR end-to-end.

Frequently Asked Questions about auto-github-contributor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate finding and fixing good first issues on GitHub repositories?

You can automate finding good first issues by scanning target repositories for labeled issues and quick-wins, then driving a TDD development loop until lint, typecheck, and tests pass before opening a pull request via the GitHub CLI.

How does test-driven development automation work for open-source contributions?

TDD automation for open-source contributions works by iterating on tests, implementation, and refactoring within a guided loop until all quality gates, including lint, typecheck, and tests, are green before submitting a pull request.

Do I need the GitHub CLI installed to automate opening pull requests?

Yes, you need the GitHub CLI installed to automate opening pull requests, because the workflow relies on gh pr create to submit changes and return the resulting PR URL for review.

Can I discover quick-win tasks like missing tests and TODOs across any GitHub repository?

Yes, you can discover quick-win tasks like missing tests, typos, i18n gaps, and TODOs across any GitHub repository by resolving a target and forking workflow, then presenting a ranked candidate list of issues.

What is the best way to ensure my automated code changes pass repository quality gates?

The best way to ensure automated code changes pass repository quality gates is to run a TDD-style loop that iterates on implementation and tests until lint, typecheck, and tests are all green before opening a pull request.

What are the limitations of automating OSS contributions with TDD loops?

Limitations include dependency on GitHub CLI, Git, jq, Python3, and optionally ripgrep, meaning the automation requires these tools pre-configured and may struggle with repositories lacking clear test frameworks or standard quality gates.