Agent skill

PR Workflow

by kmworks in kmworks/kmreader

Create and merge KMReader GitHub pull requests. An agent skill from kmworks/kmreader.

MITAuto-check passedDevelopment

Install PR Workflow

skills CLI
$ npx skills add kmworks/kmreader --skill pr-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kmworks/kmreader pr-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kmworks/kmreader.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-workflow .claude/skills/pr-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-workflow
GitHub stars
111
Token cost
~899 tokens
SKILL.md length
419 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Create and merge KMReader GitHub pull requests. An agent skill from kmworks/kmreader.

  • Works in 5 steps: Commit and git push -u origin .… → Write the body to a file and create the… → Body sections by change type → …
  • Asked to open a PR
  • SKILL.md covers Ground Rules, Open a PR and Merge a PR
  • Calls git, gh and make

What it does

PR Workflow is an agent skill from kmworks/kmreader. Create and merge KMReader GitHub pull requests. Use when asked to open a PR, push local changes for review, or merge an existing PR — including composing the squash merge message.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub, iOS and macOS. The repository describes itself as: A full-featured, native Komga client for iOS, macOS, and tvOS. The licence is MIT.

When your agent uses it

  • Asked to open a PR
  • Push local changes for review
  • Merge an existing PR — including composing the squash merge message

Example prompts

  • “/pr-workflow”

Workflow steps

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

  1. Commit and git push -u origin . Intermediate commits may be work-in-progress; only the squash message lands on main.
  2. Write the body to a file and create the PR with gh pr create --body-file; never pass a Markdown body inline
  3. Body sections by change type
  4. Link issues deliberately: Closes #N only when merging completes the whole issue; otherwise Part of #N.
  5. Open ready for review; pass --draft only when the user asks. Report the PR URL.

What it can do on your machine

Read from SKILL.md and the folder at commit cb2d394. 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
    • make

    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

PR Workflow loads about 899 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 419 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~899

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 kmworks/kmreader at commit cb2d394, republished under its MIT licence (© kmworks). 419 words, ~899 tokens.

Download SKILL.mdSave it as .claude/skills/pr-workflow/SKILL.md (or your agent's skills folder).
name
pr-workflow
description
Create and merge KMReader GitHub pull requests. Use when asked to open a PR, push local changes for review, or merge an existing PR — including composing the squash merge message.

KMReader PR Workflow

Conventions for opening and merging PRs in this repo. Release-copy and version-cycle PRs follow ../appstore-release/SKILL.md instead.

Ground Rules

  • All git-facing text is English: commits, PR titles and bodies, review comments.
  • Conventional-commit titles with a scope: fix(reader): ..., feat(browse): ..., refactor(offline): ....
  • All changes land via PR.
  • A make bump commit rides inside the feature/fix PR — that is the normal delivery flow, not a separate PR. Skip it only when the user says so.
  • Validate before opening: make format, then make build (all platforms). When localization keys changed, also make localize and fill translations per ../localization/SKILL.md.

Open a PR

  1. Sync and branch:
bash
git fetch origin
git switch -c <type>/<short-topic> origin/main

Name the branch after the title scope, e.g. fix/reader-end-page-cover.

  1. Commit and git push -u origin <branch>. Intermediate commits may be work-in-progress; only the squash message lands on main.
  2. Write the body to a file and create the PR with gh pr create --body-file; never pass a Markdown body inline:
bash
cat > /tmp/kmreader-pr-body.md <<'EOF'
...
EOF
gh pr create --title "<conventional title>" --body-file /tmp/kmreader-pr-body.md
  1. Body sections by change type:
    • fix: ## Problem (add ## Root cause when non-obvious) → ## Fix → ## Validation
    • feat / refactor: ## What → ## Why → ## Validation
    • Validation lists the commands actually run and their results (make build per platform, simulator or manual checks). There are no XCTest targets in this repo; state how behavior was verified.
    • End with Includes \make bump` to build NNN.` when a bump commit is included.
  2. Link issues deliberately: Closes #N only when merging completes the whole issue; otherwise Part of #N.
  3. Open ready for review; pass --draft only when the user asks. Report the PR URL.
Show full SKILL.md (169 more words)Show less

Merge a PR

  1. Gate on green CI and a clean merge state:
bash
gh pr checks <N>
gh pr view <N> --json mergeable,mergeStateStatus

iOS / macOS / tvOS checks must all pass and the state must be CLEAN. When checks are red, fix and push again; merge red only on explicit user instruction.

  1. Squash merge with a freshly composed message — never the auto-generated commit list. Write the body as a self-contained summary of the merged change: what user-visible behavior changed and why, plus side effects worth knowing later (removed localization keys, migrations, follow-ups). ../changelog/SKILL.md generates App Store notes from main's commit bodies (%s + %b between the latest tag and HEAD), so this message is the changelog source material: behavior first, file/class names only when they aid understanding. The PR discussion stays on GitHub; the commit must stand alone.

  2. Merge and clean up. Like PR creation, the body goes through a file — never inline a Markdown body into --body:

bash
cat > /tmp/kmreader-merge-body.md <<'EOF'
<summary from step 2>
EOF
gh pr merge <N> --squash --delete-branch \
  --subject "<conventional title> (#N)" \
  --body-file /tmp/kmreader-merge-body.md

git fetch --prune origin
git switch main
git pull --ff-only origin main
  1. Done when: main contains the squash commit with the new message, and both remote and local feature branches are gone.

© kmworks, 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 .agents/skills/pr-workflow of kmworks/kmreader.

Open the folder on GitHubat commit cb2d394

Compare with similar skills

PR Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Workflow this skillkmworks/kmreader111—~899Automated safety check: PassMIT
PR Writermicrosoft/SwiftStreamingMarkdown378—~2.9kAutomated safety check: PassMIT
Submit Aetherkiri Cross Repo PRsAetherKiri/Aether149—~1.9kAutomated safety check: PassGPL-3.0
Debug Os Failure On GitHubstrands-agents/box110—~1.3kAutomated safety check: NotesApache-2.0
Ship PRopenbootdotdev/openboot275—~3.6kAutomated safety check: WarnMIT
Reviewing Changesbitwarden/ios695—~1.1kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Writer

    microsoft/SwiftStreamingMarkdown

    Official

    Prepare and publish SwiftStreamingMarkdown pull requests end-to-end: generate PR description, commit changes, create/push branch, and open a PR when needed.

    378 GitHub stars~2.9k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Prepare, validate, push, open, monitor, and merge paired pull requests across the public AetherKiri repository and private AetherInternal package without publishing private source or unrelated…

    149 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Debug Os Failure On GitHub

    strands-agents/box

    Debug a CI failure on an OS you are not on (you are on Linux, it fails on macos-latest, or the reverse) without opening a pull request per attempt.

    110 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Ship PR

    openbootdotdev/openboot

    A skill your agent uses when the user is done editing and wants to ship the current branch via a pull request — phrases like "open a PR", "ship it", "ship this", "submit the PR", "let's send it"…

    275 GitHub stars~3.6k tokensUpdated 14 days ago
    DevelopmentAuto-check: warnings
  • Reviewing Changes

    bitwarden/ios

    Official

    Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.

    695 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

More from kmworks/kmreader

All 8 skills in this repo
  • Appstore Release

    kmworks/kmreader

    Coordinate the KMReader App Store release workflow. An agent skill from kmworks/kmreader.

    111 GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Localization

    kmworks/kmreader

    A skill your agent uses when updating KMReader translations in Localizable.xcstrings after code changes.

    111 GitHub stars~800 tokensUpdated today
    Auto-check passed
  • Simulator

    kmworks/kmreader

    A skill your agent uses when observing or driving an iOS simulator for KMReader debugging — screenshots, accessibility tree, tap/swipe/gestures, hardware buttons, orientation, and unified logs via…

    111 GitHub stars~797 tokensUpdated today
    Auto-check passed
  • Testflight

    kmworks/kmreader

    Distribute KMReader builds to TestFlight groups via the asc CLI.

    111 GitHub stars~403 tokensUpdated today
    Auto-check passed
  • Changelog

    kmworks/kmreader

    Generate App Store changelog text from commits between the latest tag and HEAD.

    111 GitHub stars~370 tokensUpdated today
    Auto-check passed
  • Repo Conventions

    kmworks/kmreader

    KMReader subsystem conventions and invariants — reader state boundaries, reading-progress sync, offline downloads and caching, local database (GRDB) migrations, SSE dispatch, browse and dashboard…

    111 GitHub stars~18k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about PR Workflow

What does PR Workflow do?

Create and merge KMReader GitHub pull requests. An agent skill from kmworks/kmreader. PR Workflow is an agent skill from kmworks/kmreader. Create and merge KMReader GitHub pull requests.

When should I use PR Workflow?

PR Workflow fits situations like: asked to open a PR; push local changes for review; merge an existing PR — including composing the squash merge message.

How do I install PR Workflow in Claude Code?

Run `npx skills add kmworks/kmreader --skill pr-workflow -a claude-code`. Or copy the skill folder (.agents/skills/pr-workflow in kmworks/kmreader) into .claude/skills/pr-workflow in your project. Claude Code loads it when a task matches its description.

How do I install PR Workflow in Codex?

Run `npx skills add kmworks/kmreader --skill pr-workflow -a codex`. Or copy the skill folder (.agents/skills/pr-workflow in kmworks/kmreader) into .agents/skills/pr-workflow in your project. Codex loads it when a task matches its description.

Can I use PR Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kmworks/kmreader --skill pr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-workflow, .gemini/skills/pr-workflow, .github/skills/pr-workflow and .opencode/skills/pr-workflow in your project.

What does PR Workflow need to run?

Going by SKILL.md and its folder, PR Workflow needs the command-line tools its instructions call (git, gh and make).

Does PR Workflow access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Workflow use?

PR Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Workflow use?

About 899 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Workflow?

Skills that share tags, products or a category with PR Workflow: PR Writer (microsoft/SwiftStreamingMarkdown, 378 stars), Submit Aetherkiri Cross Repo PRs (AetherKiri/Aether, 149 stars), Debug Os Failure On GitHub (strands-agents/box, 110 stars) and Ship PR (openbootdotdev/openboot, 275 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Workflow?

kmworks (a GitHub organization) maintains it in kmworks/kmreader, which has 111 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.

Source: kmworks/kmreader on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.