Github pr workflow
Skill Martin-Hausleitner/martins-awesome-skills/skills/github/github-pr-workflow
Martin's Awesome Skills: public-safe Hermes and OpenClaw agent skills with Telegram approval workflows
npx -y skills add Martin-Hausleitner/martins-awesome-skills --skill github-pr-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when creating, updating, reviewing, testing, or merging a GitHub pull request
SKILL.md
1.0 KB, as published. Nobody here has run it
GitHub PR Workflow
Overview
Keep pull request work reviewable: one branch, one purpose, clear tests, and a concise body.
Workflow
- Inspect status:
git status --short --branch
git remote -v
- Create a branch with a conventional prefix:
git checkout -b codex/short-description
- Make scoped changes and run relevant tests.
- Stage only intended files:
git add README.md docs/SKILL_CATALOG.md
git diff --cached --stat
- Commit with a precise message:
git commit -m "docs: improve public skill catalog"
- Push and open the PR:
git push -u origin HEAD
gh pr create --fill
PR Body
Include:
- Summary
- Verification
- Risk or rollback notes
- Screenshots for visible docs/site changes when useful
Safety
- Do not include private config, real credentials, private logs, or local cache files.
- Run the repo safety audit before opening public PRs.