pr-name-by-capability

Audit GitHub pull requests for driver-word naming violations on reusable capability modules.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-name-by-capability-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-name-by-capability
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/skill-archive/pr-name-by-capability
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-name-by-capability-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reusable libraries often get named after the workflow that first needed them (e.g. cert_fix, portal, export), which hides their general capability and blocks reuse. This Skill audits a GitHub PR's paths, renames, and title wording to detect driver/motive words on capability code and proposes capability-oriented renames. ## Core Features & Use Cases - PR naming audit: Fetches PR title, body, and changed/renamed paths via the GitHub CLI, then classifies each naming signal as a violation, an OK driver (queues, report routers), or out-of-scope. - Structured findings report: Emits a compact verdict report with violations, OK drivers, and suggested capability-oriented rename directions for each finding. - Mode routing: Supports preflight-proposal (isolated worktree contract), audit-only, user-directed fixes, and default rename application. - Use Case: A PR adds a cert_fix_page_indicators module that actually generates reusable page-indicator assets. The audit flags the driver word and suggests renaming toward a capability name like page indicators / home indicator pair. ## Quick Start Ask the AI to audit PR #2153 for name-by-capability violations and report any driver words on reusable modules.

Frequently Asked Questions about pr-name-by-capability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a GitHub PR for naming violations?▼

Invoke the audit with a PR number or URL, and it fetches the PR title, body, and changed or renamed paths using the GitHub CLI. Each naming signal is classified as a violation, an OK driver, or skipped, then reported with suggested rename directions.

What is the name-by-capability rule in code review?▼

The rule requires packages and modules to be named for the reusable work they perform, not the workflow that motivated them. Driver words like cert, portal, or export are acceptable only on workflow-only surfaces such as queues and report routers.

Which driver-named surfaces are acceptable in a PR audit?▼

Queue drains, report parsers, routing tables, and classification artifacts that exist solely for one workflow may keep the driver word. These are listed as OK drivers in the report rather than violations.

Does the audit require checking out the PR branch?▼

No, the audit uses gh pr view and the pulls files API with pagination, so the user's worktree stays unchanged. It explicitly avoids gh pr checkout for naming audits.

What happens when a PR expands an already misnamed package?▼

When a PR grows an existing misnamed package with new public API or callers, the offense is scored as a violation and the package name is noted. Unchanged misnamed packages outside the diff are listed under Notes as context.