autodev

Automate GitHub issue implementation from backlog to pull request.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/rnwolfe/forge --skill autodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autodev
Source: https://github.com/rnwolfe/forge/tree/main/.claude/skills/autodev
Command: npx skills add https://github.com/rnwolfe/forge --skill autodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end handling of GitHub issues: selecting, implementing in a fresh worktree, validating changes, and delivering a ready PR without manual intervention.

Core Features & Use Cases

  • End-to-end issue implementation in a new worktree, automatic build/test verification, PR generation with a structured description, guardrails to prevent conflicts and protect sensitive files.
  • Use Case: A team wants issues from backlog/ready to be implemented and merged with minimal human involvement, ensuring traceability and reproducibility.
  • Example: When a high-value backlog item is identified, the agent will create a dedicated worktree, apply changes, run tests, and open a PR.

Quick Start

Prompt the agent with /autodev to automatically pick the highest-value backlog issue and implement it end-to-end.

Frequently Asked Questions about autodev

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

FAQPage Schema
How do I automate GitHub issue implementation from backlog to pull request?

Automating GitHub issue implementation involves selecting a backlog issue, creating a fresh git worktree, applying code changes, running build verification, and generating a PR. This process ensures traceability and reproducible changes without manual intervention.

What is the best way to autonomously implement backlog issues in a git worktree?

Autonomous implementation in a git worktree works by automatically picking the highest-value issue, isolating changes in a dedicated worktree, and running tests. It enforces build verification and protects restricted files to ensure safe, auditable code modifications.

Do I need a specific configuration file to automate issue management and PR generation?

Yes, repositories must be configured with a forge.toml file. This configuration allows the automation to identify backlog or ready issues across repositories and enforce project-specific guardrails during code implementation and PR generation.

How does this autonomous issue implementation protect restricted files and prevent conflicts?

It protects restricted files and prevents conflicts by adhering to CLAUDE onboarding guidelines and enforcing strict build and test verification. These guardrails ensure that automated changes are safe, auditable, and do not alter sensitive repository files.

Can I use autonomous issue management for repositories with existing CI/CD pipelines?

Yes, autonomous issue management integrates with existing workflows by enforcing test and build verification before generating a PR. It creates a dedicated worktree to isolate changes, ensuring compatibility with your current continuous integration processes.

What are the limitations of autonomous end-to-end issue implementation?

Limitations include requiring a forge.toml configuration file and strict adherence to CLAUDE onboarding guidelines. It is designed for backlog or ready issues, meaning it may not suit repositories lacking structured issue tracking or established build verification steps.