pr-small-cl
Scope or split a pull request into a self-contained reviewable increment. Use when a user asks to "split this PR", "make this change smaller", or "small CL".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- pr-small-cl
- description
- Scope or split a pull request into a self-contained reviewable increment. Use when a user asks to "split this PR", "make this change smaller", or "small CL".
03 SKILL.md 正文
Focused Pull Request Guide
When to Use This Guide
Use this guide to plan, assess, or split a pull request into a reviewable unit. The pull request boundary is conceptual: one coherent outcome that a reviewer can understand with its context and verification.
What a Focused Pull Request Contains
A focused pull request contains the implementation, related tests, documentation, and configuration needed for one outcome. It leaves the system in a usable state and gives the reviewer the information needed to assess the change.
Use the description guide to record the scope, verification, risks, and follow-up work.
Splitting a Change
Choose a split that gives each increment a coherent purpose and a clear test boundary. Useful seams include:
- Preparation refactors followed by behavior changes.
- Independent vertical features that each deliver a user-visible capability.
- Layer-specific work when each layer remains independently understandable.
- Stacked changes when each earlier change supplies the next change's stable foundation.
State dependencies between related pull requests and keep each increment safe to merge or revert on its own.
Reviewable Scope
Ask to split a change when its breadth prevents a reliable assessment of design, behavior, or verification. Identify the first coherent increment and the remaining increments so the author has an actionable path forward.
Use reviews to evaluate the resulting scope and emergencies when an active incident sets the immediate boundary.
Responding to Review
Use the comment guide to respond to feedback and resolve pushback.
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.