auto-dev

Automate open issues to pull requests with human approval gates.

515|64|Updated Oct 23, 2024
One-click install
npx skills add https://github.com/allenhutchison/obsidian-gemini --skill auto-dev-allenhutchison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-dev
Source: https://github.com/allenhutchison/obsidian-gemini/tree/main/.agents/skills/auto-dev
Command: npx skills add https://github.com/allenhutchison/obsidian-gemini --skill auto-dev-allenhutchison

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the end-to-end workflow from open issues to automated pull requests, enabling continuous, human-guided maintenance without manual triage overhead.

Core Features & Use Cases

  • Scheduled ticks: runs unattended at regular intervals to triage issues, draft implementation plans, and open PRs.
  • Gatekeeping & human oversight: ensures plan approval and never merges PRs automatically; maintainer retains control.
  • Flexible invocation: supports scheduled runs, interactive ticks via /auto-dev, and a dry-run mode for read-only previews.

Quick Start

Run the interactive /auto-dev command to perform a single tick or schedule the script to run automatically.

Frequently Asked Questions about auto-dev

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

FAQPage Schema
How do I automate the workflow from open GitHub issues to pull requests?

Automating the issue-to-PR workflow involves scheduling regular ticks that triage open issues, draft implementation plans, and open PRs while enforcing human approvals. This enables continuous maintenance without manual triage overhead.

Can I preview automated PR planning without modifying my repository?

Yes, you can use a dry-run mode for read-only previews to see how the automation triages issues and drafts plans. This allows you to validate the behavior safely before applying any changes to your repository.

Does automated issue triage require GitHub authentication to run?

Automated issue triage requires GitHub authentication and access to repository issues and PRs data. It also requires scripts and tooling to execute a single tick via the auto-dev.sh script.

How do I run a single tick of the issue-to-PR pipeline interactively?

You can run a single tick of the issue-to-PR pipeline interactively by invoking the /auto-dev command. This triggers the automation to triage issues, prepare builds, and update PRs on demand.

Will the automated PR pipeline merge pull requests without maintainer oversight?

No, the automated PR pipeline never merges pull requests automatically and ensures maintainer control through plan approval gatekeeping. Retaining human oversight prevents unintended code changes from being merged.

What is the best way to handle continuous issue triage for a GitHub repository?

The best way to handle continuous issue triage is scheduling unattended runs at regular intervals to triage issues and draft implementation plans. This approach reduces manual overhead while keeping human approval gates intact.