github-prlisted

Automates the end-to-end Git workflow: branch creation, staging, committing, pushing, and opening or updating a GitHub pull request. Use when a feature or fix is ready for review and requires a structured PR, or when branch changes may need to be pushed to an existing PR for follow-up review.
mfmezger/ai_agent_dotfiles · ★ 1 · Code & Development · score 65

Install: claude install-skill mfmezger/ai_agent_dotfiles

# GitHub Workflow This skill guides the process of moving local changes to a GitHub Pull Request. ## Prerequisites - `git` must be installed and configured. - `gh` (GitHub CLI) must be installed and authenticated. ## Commit Message Format Use Conventional Commits with this required format: `<type>(<scope>): <summary>` - `type` REQUIRED. Common values: `feat`, `fix`, `docs`, `refactor`, `chore`, `test`, `perf`, `ci`, `build`, `style`. - `scope` REQUIRED. Short noun for the changed area (for example: `config`, `api`, `ui`, `docs`). - `summary` REQUIRED. Imperative, <= 72 chars, no trailing period. Rules: - **Never add AI attribution anywhere in the GitHub workflow.** Do not write `Generated by ...`, `Co-authored-by: Claude`, `Co-authored-by: Opus`, `Co-authored-by: Sonnet`, or any other AI/model/agent attribution. - This ban applies to commit subjects, commit bodies, commit footers, PR titles, PR bodies, and PR comments. Do not add it even if a default template, tool, model habit, or previous workflow suggests it. - Do not add sign-offs or breaking-change footers unless the user requests them. ## Workflow Steps Follow this order exactly: confirm branch state, stage, commit, push, then handle the PR. 1. **Branch Check / Creation** - Check the current branch before doing anything else. - If already on a suitable non-default working branch, stay on it. - If on a default branch such as `main` or `master`, create a feature branch first. - Iden