skills.rest
lshtram
lshtramCOMMUNITY
Explore all skills by this author →
GitHub

github-automation

Coordinate Git operations, PR creation, and GitHub Action configurations.

Updated Jan 21, 2026
Search Tags:#automation#git#github#pr#ci-cd#branch-management
One-click install
npx skills add https://github.com/lshtram/core_dev --skill github-automation-lshtram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-automation
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/github-automation
Command: npx skills add https://github.com/lshtram/core_dev --skill github-automation-lshtram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the bridge between local development and the remote repository, reducing manual Git operations and error-prone PR workflows.

Core Features & Use Cases

  • Branch Management: Enforces consistent naming like feat/<prd-id>-<slug> or fix/<prd-id>-<slug> to improve traceability.
  • PR Preparation & Traceability: Builds the PR description from REVIEW_NOTE.md and optionally includes a "Closes #[issue_number]" reference when applicable.
  • CI/CD Alignment: Verifies the presence of .github/workflows/verify.yml and ensures it runs on every push; prevents PRs from being marked Ready for Review until CI checks pass.

Quick Start

Create a feature or fix branch named feat/<prd-id>-<slug>, prepare a PR body from REVIEW_NOTE.md, and ensure CI verification passes before merging.

Frequently Asked Questions about github-automation

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

FAQPage Schema
How do I automate GitHub PR creation from local Git branches?▼

Automating GitHub PR creation from local Git branches involves coordinating branch naming, preparing the PR body from a REVIEW_NOTE.md file, and ensuring CI checks pass before marking it Ready for Review. This workflow reduces manual Git operations and enforces PRD-ID traceability.

What is the best way to enforce consistent branch naming for pull requests?▼

Enforcing consistent branch naming for pull requests requires standardized prefixes like feat/<prd-id>-<slug> or fix/<prd-id>-<slug>. This automated approach improves traceability by linking every branch directly to its corresponding product requirement document.

Can I prevent merging a pull request until CI checks pass?▼

Preventing a pull request from merging until CI checks pass involves verifying the presence of .github/workflows/verify.yml and ensuring it runs on every push. The PR is blocked from being marked Ready for Review until this CI verification is complete.

How does PR traceability work with issue linking in GitHub workflows?▼

PR traceability with issue linking works by enforcing PRD-ID references in branch names and optionally including a Closes #[issue_number] reference in the PR description built from REVIEW_NOTE.md. This ensures every merged code change is automatically linked to its originating issue.

Do I need a specific CI-CD configuration to use automated branch management?▼

Automated branch management requires a CI-CD configuration that includes a .github/workflows/verify.yml file configured to run on every push. This specific GitHub Action setup is mandatory for verifying CI readiness before any PR can be merged.

Related Skills

Explore More Software Engineering Skills→
pegasus-isipegasus-isi

create-issue

Create GitHub issues from templates and initialize linked branches and worktrees.

Official
Advanced
khwerhahnkhwerhahn

close-issue

Close GitHub issues, linked pull requests, and feature branches.

Community
Advanced
fabnfabn
1

github:actionlint

Configure actionlint CI to lint GitHub Actions workflow files on push and pull request events.

Community
Advanced
highflame-aihighflame-ai
4

git-workflow

Validate git commit messages and branch names against CI regex patterns.

Official
Advanced