AGENT SKILL

pr-name-by-capability

Audit a GitHub PR for name-by-capability violations: driver/motive words on reusable capability modules (queues and report routers may keep the driver word), then apply capability-oriented renames by default. Triggers: /pr-name-by-capability, name-by-capability audit, audit PR for naming, name by capability, capability naming review, cert_fix rename check, driver word in package name.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 7
Forks
1

01 前言 Front Matter

name
pr-name-by-capability
description
Audit a GitHub PR for name-by-capability violations: driver/motive words on reusable capability modules (queues and report routers may keep the driver word), then apply capability-oriented renames by default. Triggers: /pr-name-by-capability, name-by-capability audit, audit PR for naming, name by capability, capability naming review, cert_fix rename check, driver word in package name.

02 资源文件 5

03 SKILL.md 正文

Name-by-Capability Audit

Audit a GitHub PR against the name-by-capability rule. Inspect paths and title wording for driver or motive words on reusable capability code, and report violations with capability-oriented rename directions.

Mode routing

First-match routing selects the mode before the audit steps:

  1. preflight-proposal runs pr-name-by-capability preflight-proposal <pr_number> --base-sha <base_sha> --head-sha <head_sha> --worktree <isolated_worktree> under the shared preflight proposal contract. Record each finding with violation or OK-driver classification.
  2. audit-only is report-only and ends after the findings report.
  3. A user-supplied rename or fix direction follows the existing normal fix workflow.
  4. Normal mode applies the suggested rename direction by default.

Gotchas

  • Name reusable libraries for the action they perform; a first cert caller still leaves the library capability-named. Score reuse potential alongside the PR title.
  • Correctly driver-named surfaces (cert_fix_queue, report routing/locate, unfixable patterns) are OK findings — list them under OK drivers.
  • Renames and new paths carry the most signal; when a PR expands an already-misnamed package, note the package name too.

When this applies

  • User invokes /pr-name-by-capability <PR> or asks to audit a PR for name-by-capability / capability naming.
  • PR adds or renames packages/modules, or frames a general shared operation with a driver/motive word (cert_fix, cert_closeout, portal, export, …).

A missing PR number or URL returns exactly: Give a GitHub PR number or URL to audit for name-by-capability. Resolved targets follow Mode routing.

Constraints

  • Report findings plus a suggested rename direction for each violation.
  • Suggest renames for paths the PR touched; for an expanded offense, also name the package the PR grew.
  • Distinguish violation vs OK driver using reference/offense-examples.md.

Process

Register every bullet from reference/task-seeds.md with update_plan. Mark each complete with evidence. Follow those seeds in order — do not restate them here.

Load order for the rule: if docs/agents/name-by-capability.md exists, read it first; always keep reference/rule-checklist.md as the fallback when the doc is missing. On disagreement after the docs PR merges, prefer the repo doc and update the skill checklist in a follow-up.

Composition

Peer Relationship
pr-shared-extraction Layering and extraction (where code lives). Invoke when a path’s role is unclear; this skill only scores the name.
reviews / PR review skills May invoke this skill by name when naming is in scope

File index

File Purpose
SKILL.md Hub — gotchas, when-applies, process, composition
reference/rule-checklist.md Embedded rule + naming checklist (fallback when docs are missing)
reference/offense-examples.md Classifier + known OK drivers vs offenders
reference/fetch-commands.md Minimal gh fetch for PR naming surface
reference/report-template.md Compact report shape
reference/task-seeds.md Ordered task seeds for the audit run
../_shared/pr-loop/preflight-proposal.md Shared isolated proposal mode and evidence record
../_shared/pr-loop/preflight-proposal.contract.test.mjs Cross-skill mode and contract test

Folder map

  • SKILL.md — hub
  • reference/ — rule, examples, fetch recipe, report template, task seeds

04 同仓库更多 Skills

jl-cmd-projects
jl-cmd-projects/claude-dev-env

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'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

source-command-sr-loop

Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

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.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

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'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

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'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

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.

★ 7