pr-refinement
Coordinate shared-extraction and capability-naming audits, then update an existing pull request or publish a focused GitHub pull-request stack. Use when a user asks to turn a PR architecture audit into extracted shared code and small pull requests.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- pr-refinement
- description
- Coordinate shared-extraction and capability-naming audits, then update an existing pull request or publish a focused GitHub pull-request stack. Use when a user asks to turn a PR architecture audit into extracted shared code and small pull requests.
03 SKILL.md 正文
PR Refinement
Turn audit findings into a focused existing pull-request update or a dependency-ordered GitHub pull-request stack.
Peer skills
- Run
pr-shared-extractionfor reusable-code placement, canonical shared homes, and extraction findings. - Run
pr-name-by-capabilityfor module, symbol, path, branch, and pull-request naming findings. - Use
pr-small-clto divide approved fixes into coherent, independently reviewable pull requests.
The peer skills own their audit rules and finding priorities.
Workflow
- Run both audits in parallel against the same pull request. Keep their findings, locations, priorities, destinations, API directions, and naming directions.
- Build one change map. Group findings by shared capability and dependency.
- Use
pr-small-clto choose the delivery shape. Update the existing pull request when it remains one coherent, reviewable outcome. - Create a replacement pull-request stack when the focused-change review identifies independent increments. Give each pull request one coherent outcome, related tests, a clear verification boundary, and a capability-oriented branch and title. Close the original pull request as superseded and link the replacement stack.
- Implement the existing pull request or the replacement stack in dependency order. Earlier pull requests create stable shared foundations. Later pull requests migrate consumers and remove replaced code.
- Run scoped production-path tests for each pull request. Record commands and results.
- Commit and push each branch. Update the existing pull request, or open draft replacement pull requests in stack order and set every child pull request base to its parent.
- Include scope, verification, risks, and stack dependencies in every pull-request body.
Completion
Deliver a focused, tested, pushed existing pull request, or a replacement stack with explicit parent-child links.
04 同仓库更多 Skills
update
Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.
source-command-sr-loop
Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean
skill-builder
Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.
session-tidy
Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.
session-log
Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.
run-claude-dev-env
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.