" --body "<body>"` - Share the generated PR URL with the user. - If a PR already exists: - Do not open a duplicate PR. - After the push succeeds, add a PR comment containing exactly `/gemini review` to trigger the code quality review. - Execute: `gh pr comment <number-or-url> --body "/gemini review"` - Share the existing PR URL with the user and mention that the review trigger comment was added after pushing the new commit. ## Common Failures - **Pre-commit hooks**: If hooks fail, fix the files and stage them again before committing. - **Untracked files**: Ensure new files are added. - **Remote branch already exists**: If the branch exists, ask the user if they want to overwrite or use a different name. --- > Source: [mfmezger/ai_agent_dotfiles](https://github.com/mfmezger/ai_agent_dotfiles) — distributed by [TomeVault](https://tomevault.io). <!-- tomevault:4.0:skill

# Mfmezger AI Agent Dotfiles Github Pr > GitHub Workflow - Skill: `tomevault-io/mfmezger-ai-agent-dotfiles-github-pr` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/mfmezger-ai-agent-dotfiles-github-pr` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/mfmezger-ai-agent-dotfiles-github-pr/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/mfmezger-ai-agent-dotfiles-github-pr --- # 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` 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. - Identify the scope of changes (e.g., `feat`, `fix`, `docs`, `chore`). - Propose a branch name following the pattern `/`. - Execute when a new branch is needed: `git checkout -b ` 2. **Review & Stage Changes** - Review changes with `git status` and `git diff`. - By default, stage only the files that belong to the current requested change. - If the user provided file paths/globs, stage only those files. - If there are ambiguous extra changed files, ask before staging/committing and leave them unstaged unless the user explicitly includes them. - Stage the intended files with `git add ...`. - Optionally inspect recent subjects for local scope patterns: `git log -n 10 --pretty=format:%s`. 3. **Commit** - Propose a message in exact format: `():

`. - Execute: `git commit -m ""` - If pre-commit hooks fail, diagnose and fix the issues before re-staging and re-committing. - Do not move on to PR actions until the commit succeeds. 4. **Push** - Push the committed branch to the remote before any PR creation or review trigger. - If this is the first push for the branch, use: `git push -u origin ` - If the upstream is already set, use: `git push` - Never post `/gemini review` before the push succeeds for the latest commit. 5. **Pull Request Handling** - Only after a successful push, check whether a PR for the current branch already exists. - Use `gh pr view --json url,number,headRefName` to detect an existing PR for the checked-out branch. - If no PR exists: - Create the PR using `gh pr create`. - Provide a concise title (often the commit message) and a body summarizing the changes. - Execute: `gh pr create --title "" --body "<body>"` - Share the generated PR URL with the user. - If a PR already exists: - Do not open a duplicate PR. - After the push succeeds, add a PR comment containing exactly `/gemini review` to trigger the code quality review. - Execute: `gh pr comment <number-or-url> --body "/gemini review"` - Share the existing PR URL with the user and mention that the review trigger comment was added after pushing the new commit. ## Common Failures - **Pre-commit hooks**: If hooks fail, fix the files and stage them again before committing. - **Untracked files**: Ensure new files are added. - **Remote branch already exists**: If the branch exists, ask the user if they want to overwrite or use a different name. --- > Source: [mfmezger/ai_agent_dotfiles](https://github.com/mfmezger/ai_agent_dotfiles) — distributed by [TomeVault](https://tomevault.io).