A GitHub workflow command that turns local code changes into an issue, feature branch, commit, and pull request. A pull request is a request for others to review changes before they are merged.

Use it to check changes, create the related GitHub issue and branch, commit and push the work, and open a pull request.

It puts the repository steps in one order and stops before continuing when the configured lint or test checks fail.

How melodypapa/py-armodel configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to melodypapa/py-armodel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/melodypapa/py-armodel/main/.claude/commands/gh-workflow.md

Clone the repo

git clone --depth 1 https://github.com/melodypapa/py-armodel

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/melodypapa/py-armodel/gh-workflow/github.svg)](https://agentmods.dev/commands/melodypapa/py-armodel/gh-workflow)

Your own site

<a href="https://agentmods.dev/commands/melodypapa/py-armodel/gh-workflow"><img src="https://agentmods.dev/badge/commands/melodypapa/py-armodel/gh-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/melodypapa/py-armodel/gh-workflow"><img src="https://agentmods.dev/badge/commands/melodypapa/py-armodel/gh-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 844 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00844
Opus 5.5	$0.00000	$0.00338
Sonnet 5.5	$0.00000	$0.00169
Haiku 4.5	$0.00000	$0.00084

Measured 5d ago against content hash 8eddd4502d4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gh-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/gh-workflow.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Workflow Automation

Automate the complete GitHub workflow for creating issues, feature branches, commits, and pull requests.

Workflow Steps

When the user runs /gh-workflow, perform the following steps in order:

1. Quality Checks (Must Pass Before Proceeding)

Run linting with flake8: flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
Run tests with pytest: pytest
Install package: pip install -e .
All checks must pass before proceeding to next step
If any checks fail, report errors and ask user if they want to:
- Abort the workflow
- Fix issues and retry
- Continue anyway (not recommended)

Display quality gate summary table:

Check        Status    Details
───────────────────────────────────
Flake8       ✅ Pass    No E9,F63,F7,F82 errors
Pytest       ✅ Pass    All tests passed

2. Analyze Current Changes

Run git status to see modified files
Run git diff to review unstaged changes
Ask the user for a brief summary of the changes if not clear from the diff

3. Create GitHub Issue

Create a GitHub issue using gh issue create
Title format: "<type>: <brief description>" (type can be: feat, fix, docs, refactor, test, chore)
Include sections: Summary, Changes, Files Modified, Test Coverage, Requirements (if applicable)
Capture the issue number (e.g., #20)

4. Create Feature Branch

Create and checkout a new feature branch
Branch naming convention: feature/<requirement-id>-short-description or feature/<type>-short-description
Example: feature/swr-writer-00006-class-file-structure or feature/add-new-parser

5. Stage and Commit Changes

Stage all relevant modified files
Create a commit with:
- Conventional commit format: <type>: <description>
- Detailed commit body describing changes
- Reference to the issue (e.g., Closes #20)
- Important: Do NOT add Claude as co-author (no Co-Authored-By line)

6. Push to GitHub Only

Push the branch to GitHub remote (origin)
Important: Do NOT push to gitee remote
Use explicit GitHub URL if needed: git push [email protected]:melodypapa/autosar-pdf.git

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 100 lines · 0 tokens per session scan A 8eddd4502d4e

Subscribe to this mod's changes

gh-workflow is a command published in the GitHub repository melodypapa/py-armodel (18 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 844 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-01.

Commits Git and workflow arxml autosar parser writer

gh-workflow next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gh-workflowmelodypapa/py-armodel	Command	18	14d ago	MIT	A	0	Claude Code
standupvvedantb/eva	Command	101	yesterday	MIT	A	0	Claude Code
gitazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	20	Claude Code
session-reportdamusix/atomic-claude	Command	115	5d ago	MIT	A	31	Claude Code
git-workflowHermeticOrmus/LibreUIUX-Claude-Code	Command	115	1mo ago	MIT	A	14	Claude Code
commitjoaquimscosta/arkhe-claude-plugins	Command	22	22d ago	MIT	A	11	Claude Code
step6-shipsrnichols/plan-forge	Command	6	2d ago	MIT	A	26	GitHub Copilot

py-armodel: Command for Claude Code