skills.rest
zcancio
zcancioCOMMUNITY
Explore all skills by this author →
GitHub

spec-to-merge

Create GitHub issues from specs and auto-merge pull requests after local checks.

Updated Feb 13, 2026
Search Tags:#automation#ci/cd#code review#pull request#github#development pipeline
One-click install
npx skills add https://github.com/zcancio/aide --skill spec-to-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-merge
Source: https://github.com/zcancio/aide/tree/main/.claude/skills/spec-to-merge
Command: npx skills add https://github.com/zcancio/aide --skill spec-to-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and commands (resource) components.

What problem does it solve?

This Skill streamlines the process of turning a specification into a merged pull request, ensuring code quality and efficient delivery through a two-phase pipeline.

Core Features & Use Cases

  • Automated Implementation: Generates GitHub issues and triggers AI to implement specs.
  • Manual Testing Gap: Provides a clear break for manual testing before merging.
  • Automated Checks & Merge: Runs linters, tests, and security scans before enabling auto-merge.
  • Use Case: You have a new feature documented in a spec file. Use this Skill to have the AI create the code, open a PR, and then, after you've tested it locally, automatically run all checks and merge it.

Quick Start

Use the spec-to-merge skill to implement the spec in docs/new_feature.md.

Frequently Asked Questions about spec-to-merge

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

FAQPage Schema
How do I automate creating a pull request from a specification file?▼

You can automate pull request creation from a specification by using a two-phase pipeline that generates a GitHub issue, triggers an AI to implement the spec on a new branch, and opens a pull request.

What is a two-phase development pipeline for GitHub pull requests?▼

A two-phase development pipeline separates automated implementation from automated merging. Phase 1 creates a GitHub issue and AI-generated pull request, while Phase 2 runs local checks and enables auto-merge only after manual testing is complete.

How do I run local CI checks before enabling auto-merge on a pull request?▼

You can run local CI checks before enabling auto-merge by executing shell scripts that mirror CI validation. The pipeline runs linting, formatting, security scanning, and unit tests, then enables auto-merge upon successful validation.

Does the spec-to-merge pipeline require the GitHub CLI to manage issues and PRs?▼

Yes, the spec-to-merge pipeline requires the GitHub CLI to manage issues and PRs. It directly integrates with the GitHub CLI to automate the creation of issues, management of pull requests, and the auto-merge process.

Can I manually test code before the automated merge process happens?▼

Yes, you can manually test code before the automated merge process happens. The pipeline explicitly provides a manual testing gap between Phase 1 implementation and Phase 2 local validation, ensuring you verify the feature locally before auto-merge.

What are the limitations of automating code implementation from a spec?▼

Automating code implementation from a spec requires a manual testing gap before merging, meaning it does not automatically deploy unverified code. It strictly relies on GitHub CLI integration and successful local shell script execution for linting, formatting, and security scanning.

Related Skills

Explore More Software Engineering Skills→
stribusstribus
1

create-github-pull-request-from-specification

Create draft GitHub pull requests from specification files using a pull request template.

Community
Advanced
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
heyu-aiheyu-ai

ci-triage

Diagnose CI pipeline failures in Python, JavaScript, and Go stacks.

Official
Intermediate
HorusGoulHorusGoul
8

land

Merge pull requests by resolving conflicts, checking CI/CD, and squashing via GitHub API.

Community
Advanced