GitHub PR Workflow

What it does

When your agent uses it

• Updating a PR after review
• Preparing review-ready diffs
• Managing draft versus ready states
• Landing changes with clear validation and risk notes

Example prompts

• “/github-pr-workflow”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

1. 1Start from the correct base branch.
2. 2Keep the branch scope tight.
3. 3Make coherent commits.
4. 4Validate before opening the PR.
5. 5Open a draft PR if the implementation is not review-ready.
6. 6Write a useful PR title and description.
7. 7Address review comments with focused follow-up commits.
8. 8Re-validate before merge.
9. 9Merge with the right strategy.

What it can do on your machine

Read from SKILL.md and the folder at commit 8107e89. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • gh

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub PR Workflow loads about 1.4k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 636 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~69

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AlexAI-MCP/hermes-CCC at commit 8107e89, republished under its MIT licence (© AlexAI-MCP). 636 words, ~1,379 tokens.

name

github-pr-workflow

description

Run a disciplined GitHub pull request workflow from branch creation through merge. Use when opening a PR, updating a PR after review, preparing review-ready diffs, managing draft versus ready states, or landing changes with clear validation and risk notes.

version

0.1.0

author

OpenAI Codex

license

MIT

metadata.category

github

metadata.ported_from

NousResearch Hermes Agent

metadata.tags

github, pull-request, workflow, collaboration

metadata.tools

git, github, shell

metadata.maturity

beta

## Summary
- ...

## Why
- ...

## Testing
- `pytest tests/test_auth.py::test_login_redirect_does_not_loop_when_session_is_hydrated -vv`

## Risks
- ...

git checkout -b fix-auth-redirect-loop
git status --short
git diff --stat
gh pr create --draft --title "Fix auth redirect loop during token refresh" --body-file PR_BODY.md
gh pr view --web

PR workflow status:
- Branch: fix-auth-redirect-loop
- State: draft
- Summary: auth middleware now waits for hydrated session token before redirecting
- Validation: targeted auth regression test passed
- Remaining blocker: reviewer input needed on fallback behavior during refresh timeout

© AlexAI-MCP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/github-pr-workflow of AlexAI-MCP/hermes-CCC.

Open the folder on GitHubat commit 8107e89