Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
Integrations
Yeet
Try itStage, commit, and open PR
What it does
Require GitHub CLI . Check . If missing, ask the user to install and stop. Require authenticated session. Run . If not authenticated, ask the user to run (and re-run ) before continuing.
The skill document
Prerequisites
- Require GitHub CLI
gh. Checkgh --version. If missing, ask the user to installghand stop. - Require authenticated
ghsession. Rungh auth status. If not authenticated, ask the user to rungh auth login(and re-rungh auth status) before continuing.
Naming conventions
- Branch:
pe/{description}when starting from main/master/default. - Commit: conventional commit syntax, for example
fix: handle missing config. - PR title: conventional commit syntax summarizing the full diff, for example
fix: handle missing config.
Workflow
- If on main/master/default, create a branch:
git checkout -b "pe/{description}" - Otherwise stay on the current branch.
- Confirm status, then stage everything:
git status -sbthengit add -A. - Commit tersely with a conventional commit message:
git commit -m "{type}: {description}" - Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
- Push with tracking:
git push -u origin $(git branch --show-current) - If git push fails due to workflow auth errors, pull from master and retry the push.
- Open a PR and edit title/body to reflect the description and the deltas:
GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current) - Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
- PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.
Related skills
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Save, search, and manage personal notes and knowledge bases in Get笔记 on explicit request.
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
More from patrick-erichsen-2
Browse all skillsPublish local changes to a GitHub pull request and keep working the PR until review feedback is addressed and required checks are green. Use when the user in...
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful...
Find, compare, and add Notion Marketplace templates with linked free shortlists, explicit workspace selection, browser-driven duplication, and Notion API verification.
Plan, audit, and safely execute Google Workspace admin, Gmail, Calendar, Drive, Groups, and user lifecycle work. Use when Codex is asked to help with Workspa...
Use when the user asks to create, rewrite, or structure a concise one-week sprint plan, engineering sprint plan, focused project plan, or alignment doc with...
Find, classify, and update hardcoded default-like model references in a repo. Use when the user wants to replace model strings, audit model defaults, central...