skills.rest
Mikeys-Tech-Lab
Mikeys-Tech-LabOFFICIAL
Explore all skills by this author →
GitHub

github-automation

Guide GitHub feature development with branch, commit, and PR workflows.

3|Updated Feb 17, 2026
Search Tags:#pull request#conventional commits#github flow#reasoning trace#release please#git branch strategy
One-click install
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill github-automation-mikeys-tech-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-automation
Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/github-automation
Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill github-automation-mikeys-tech-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy Git history and unclear PRs by enforcing a consistent GitHub workflow, including branch strategy, commit discipline, reflective close-out, and context-rich PR descriptions.

Core Features & Use Cases

  • GitHub Flow lifecycle: Executes a structured three-phase workflow (Start, Work, Close) for any non-trivial change.
  • Conventional Commits enforcement: Guides commit formatting and version-bump expectations aligned with Release Please.
  • Context-traced PRs: Maintains a reasoning-based PR description with required sections, updated on every push.
  • Operational safety checks: Uses build/test verification and a pre-PR security scan for PR description leakage.
  • Release automation awareness: Covers Release Please mechanics, package attribution, and deployment triggers.

Quick Start

Use github-automation before starting work by planning your phase (Start), creating a feature branch with the correct naming pattern, and committing changes using Conventional Commits so your PR includes a complete reasoning trace.

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 Flow from branch creation through pull request?▼

Automating GitHub Flow requires a structured three-phase workflow: Start, Work, and Close. This process enforces correct branch naming, Conventional Commits discipline, build and test verification, and a pre-PR security scan before creating a context-traced pull request.

Can I enforce Conventional Commits and Release Please versioning for pull requests?▼

Yes, Conventional Commits formatting and version-bump expectations aligned with Release Please are enforced during the Work phase. This ensures commit messages follow standardized formatting rules, automatically triggering appropriate package attribution and deployment automation.

What's the best way to include reasoning traces in pull request descriptions?▼

Including reasoning traces in pull request descriptions is handled by maintaining a context-rich PR document updated on every push. The workflow enforces required PR description sections that capture reflective closure and logical reasoning throughout the feature development lifecycle.

Does this GitHub workflow automation run security checks before creating a pull request?▼

Yes, a pre-PR security scan is executed as a deterministic safety constraint. This scan specifically checks for sensitive information leakage in the pull request description before posting the final PR to the GitHub repository.

How do I validate branches and build status before posting a pull request?▼

Branch and phase validation alongside build and test verification are applied as operational safety checks. These deterministic checks ensure workspace integrity and confirm that all relevant tests pass before transitioning between workflow phases or creating a pull request.

What is the GitHub Flow lifecycle for non-trivial feature development?▼

The GitHub Flow lifecycle for non-trivial work is a three-phase process: Start, Work, and Close. It guides feature development from initial branch creation through commit discipline and reflective closure, culminating in a pull request with a complete reasoning trace.

Related Skills

Explore More Software Engineering Skills→
berkcangumusisikberkcangumusisik
11

pr-create

Generate GitHub pull requests from the current branch with gh.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

changelog-generator

Generate changelogs from Git commits in Markdown format.

Community
Intermediate
infantesromeroadrianinfantesromeroadrian

pentest-cicd-redteam

Automates security assessments and red teaming in CI/CD pipelines via GitHub Actions, GitLab CI, Jenkins, and scanning tools.

Community
Advanced
AmidVoshakulAmidVoshakul

git-advanced-workflows

Optimize Git history via interactive rebasing, cherry-picking, and automated bisecting.

Community
Advanced