infra-github-operations

Synchronize markdown backlog items into GitHub pull requests, issues, and releases.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill infra-github-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-github-operations
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/infra-github-operations
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill infra-github-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve?

Keep repository-managed markdown backlog, story state, and release notes authoritative while projecting operational state into GitHub surfaces so teams can use GitHub for reviews, projects, and releases without losing traceability.

Core Features & Use Cases

  • Manage draft and ready-for-review pull requests from local backlog items and active branches.
  • Create or update GitHub issues, apply consistent labels and milestones, and add items to GitHub Projects.
  • Generate draft GitHub Releases from repository-managed release notes and attach release assets.
  • Use Case: Turn a local story into a draft PR with a review packet, synchronize a bug report into GitHub with proper labels, or publish a draft release for human approval.

Quick Start

Run the infra-github-operations skill to create a draft PR from a backlog item or sync a backlog item to GitHub.

Frequently Asked Questions about infra-github-operations

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

FAQPage Schema
How do I sync a local markdown backlog to GitHub issues and pull requests?

To sync local markdown backlog items to GitHub, this skill mirrors stories and bug reports into GitHub issues and draft pull requests. It requires backlog items under execution-plan/backlog and a tracked labels manifest to automate PR lifecycle and issue synchronization.

How do I generate draft GitHub releases from repository-managed release notes?

Draft GitHub releases can be generated from repository-managed markdown release notes using this skill. It attaches release assets and requires human review gates before publishing, ensuring the local repository remains the authoritative source for release tracking.

Do I need GitHub CLI access to automate pull request lifecycle management from a local backlog?

Yes, GitHub CLI access is required to automate pull request lifecycle management. The skill uses the gh-cli to create draft and ready-for-review PRs, apply consistent labels, and add milestones directly from your active branches and backlog items.

Can I apply consistent GitHub labels and milestones to issues generated from a markdown backlog?

Yes, you can apply consistent GitHub labels and milestones to issues generated from a markdown backlog. The skill creates or updates GitHub issues and adds them to GitHub Projects by reading a tracked labels manifest alongside your local execution-plan.

What is the best way to maintain markdown backlog traceability while using GitHub for project management?

The best way to maintain markdown backlog traceability is to keep the repository-managed story state authoritative while projecting operational state into GitHub. This skill synchronizes bug tracking and release notes into GitHub surfaces without losing local traceability.

Are human review gates required before publishing draft GitHub releases from local release notes?

Yes, human review gates are required before publishing draft GitHub releases. The skill generates draft releases from repository-managed notes and attaches assets, but it enforces a human approval step to ensure operational state is verified before publication.