New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR Scope Responsibility

by AliceJump in AliceJump/ok-end-field

Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points.

AGPL-3.0Auto-check passedDevelopment

Install PR Scope Responsibility

skills CLI
$ npx skills add AliceJump/ok-end-field --skill pr-scope-responsibility -a claude-code

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

GitHub CLI
$ gh skill install AliceJump/ok-end-field pr-scope-responsibility --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/AliceJump/ok-end-field.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-scope-responsibility .claude/skills/pr-scope-responsibility && 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-scope-responsibility
GitHub stars
556
Token cost
~1.1k tokens
SKILL.md length
559 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points.

  • Works in 5 steps: Identify the PR's stated goal from its… → Classify the actual diff into… → For each concern, state its independent… → …
  • Deciding whether a PR mixes independent reasons to change
  • SKILL.md covers Core rule, What to inspect, Core logic versus diagnostics and PR scope consistency, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

PR Scope Responsibility is an agent skill from AliceJump/ok-end-field. Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points. Use when deciding whether a PR mixes independent reasons to change, whether diagnostics should be separated from core logic, or whether the advertised PR scope matches the actual diff.

Its SKILL.md is about 1.1k 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. The repository describes itself as: 终末地 End Field Automation 基于ok-script开发的自动化. The licence is AGPL-3.0.

When your agent uses it

  • Deciding whether a PR mixes independent reasons to change
  • Whether diagnostics should be separated from core logic
  • Whether the advertised PR scope matches the actual diff

Example prompts

  • “/pr-scope-responsibility”

Workflow steps

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

  1. Identify the PR's stated goal from its title and description.
  2. Classify the actual diff into behavior-changing concerns, diagnostics/observability, configuration, persistence/formatting…
  3. For each concern, state its independent reason to change. Treat concerns as separate responsibilities only when they can reasonably…
  4. Check whether the diff changes behavior that the PR description does not disclose. Changes to thresholds, candidate selection, scheduling…
  5. Prefer the smallest useful boundary. Do not demand new classes, interfaces, design patterns, or files merely to satisfy an abstract…

What it can do on your machine

Read from SKILL.md and the folder at commit 31604a6. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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 Scope Responsibility loads about 1.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 559 words of instructions outside code blocks.

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

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 AliceJump/ok-end-field at commit 31604a6, republished under its AGPL-3.0 licence (© AliceJump). 559 words, ~1,137 tokens.

Download SKILL.mdSave it as .claude/skills/pr-scope-responsibility/SKILL.md (or your agent's skills folder).
name
pr-scope-responsibility
description
Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points. Use when deciding whether a PR mixes independent reasons to change, whether diagnostics should be separated from core logic, or whether the advertised PR scope matches the actual diff.

PR Responsibility And Scope Review

Core rule

Judge responsibility boundaries by independent reasons to change, not by file length, function count, or diff size alone.

A large module may still have one coherent responsibility. A small module may already mix unrelated responsibilities. Do not recommend splitting unless there are at least two independently changing concerns and a concrete maintenance, testing, runtime, or release risk caused by keeping them coupled.

What to inspect

  1. Identify the PR's stated goal from its title and description.
  2. Classify the actual diff into behavior-changing concerns, diagnostics/observability, configuration, persistence/formatting, concurrency/runtime infrastructure, tests, and documentation as applicable.
  3. For each concern, state its independent reason to change. Treat concerns as separate responsibilities only when they can reasonably evolve, fail, be reviewed, or be released independently.
  4. Check whether the diff changes behavior that the PR description does not disclose. Changes to thresholds, candidate selection, scheduling, state transitions, persistence semantics, or public contracts are behavior changes even when introduced alongside diagnostics.
  5. Prefer the smallest useful boundary. Do not demand new classes, interfaces, design patterns, or files merely to satisfy an abstract interpretation of SRP.

Core logic versus diagnostics

Core business logic may produce structured diagnostic evidence and call a diagnostic boundary, but should not also own independently evolving diagnostic mechanisms such as:

  • live overlays;
  • image or trace annotation;
  • diagnostic file formats;
  • file persistence and retention;
  • background writers, queues, or worker lifecycle;
  • diagnostic-only failure handling.

Ordinary configuration registration and thin orchestration are not, by themselves, responsibility violations.

Diagnostics must not change the core decision result or state progression. Diagnostic failures must fail soft unless the feature explicitly defines otherwise. On hot paths, inspect synchronous work such as copying, annotation, serialization, and queue submission; do not equate asynchronous disk I/O with fully asynchronous diagnostics.

Show full SKILL.md (263 more words)Show less

PR scope consistency

Compare the advertised scope with the actual diff.

  • If a PR says it only adds logs, debugging, or visualization but also changes thresholds, filtering, scheduling, state semantics, persistence, or contracts, flag the mismatch.
  • If multiple modules change for one clearly stated objective and the description discloses the behavior changes with separate tests, do not require a split merely because several files or modules are involved.
  • Prefer splitting when independent concerns have meaningfully different risk, validation, rollout, or review paths. A prerequisite/follow-up stack is often better than a broad refactor.

Evidence required before claiming mixed responsibilities

When reporting a responsibility-boundary problem, include all of the following:

  1. the concrete functions or modules involved;
  2. at least two independent reasons to change;
  3. the actual maintenance, testing, runtime, or release risk caused by the coupling;
  4. the minimum viable split or boundary;
  5. whether the issue is newly introduced or materially worsened by the current PR.

Do not require the PR to clean up unrelated historical coupling.

Use one of these outcomes instead of a generic "violates SRP" label:

  • Keep together — one objective, coupled validation, no meaningful independent change reason.
  • Clarify scope — implementation is coherent, but title/description understate behavior changes.
  • Extract a boundary — one PR can remain, but implementation should move an independently changing concern behind a module/function boundary.
  • Split prerequisite/follow-up — concerns have distinct behavior/risk and should be independently reviewed or merged.
  • Defer historical cleanup — coupling predates the PR and is not materially worsened here.

When CodeRabbit is involved, also read ../ok-script-pr-review/SKILL.md for triggering, waiting, replying, and resolving review threads.

© AliceJump, AGPL-3.0. 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-scope-responsibility of AliceJump/ok-end-field.

Open the folder on GitHubat commit 31604a6

Compare with similar skills

PR Scope Responsibility 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 Scope Responsibility compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Scope Responsibility this skillAliceJump/ok-end-field556—~1.1kAutomated safety check: PassAGPL-3.0
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

More from AliceJump/ok-end-field

All 14 skills in this repo

  • Ok Script I18n

    AliceJump/ok-end-field

    Maintain gettext translations for ok-script task UI and runtime messages.

    556 GitHub stars~828 tokensUpdated today
    Auto-check passed

  • Deploy

    AliceJump/ok-end-field

    Commit validated changes, calculate an annotated stable/beta/alpha version tag, and push the release to the publishing remote.

    556 GitHub stars~625 tokensUpdated today
    Auto-check passed

  • GitHub Rulesets

    AliceJump/ok-end-field

    Diagnose or configure GitHub branch/tag rulesets on ok-script repos.

    556 GitHub stars~595 tokensUpdated today
    Auto-check passed

  • Use Local Venv

    AliceJump/ok-end-field

    Prefer the repository-local Python virtual environment for coding-agent work.

    556 GitHub stars~688 tokensUpdated today
    Auto-check passed

  • Ok Script PR Review

    AliceJump/ok-end-field

    Triage CodeRabbit reviews on ok-script pull requests. An agent skill from AliceJump/ok-end-field.

    556 GitHub stars~904 tokensUpdated today
    Auto-check passed

  • Ok Script Tasks

    AliceJump/ok-end-field

    Create, modify, register, or review ok-script BaseTask and TriggerTask classes.

    556 GitHub stars~619 tokensUpdated today
    Auto-check passed

Categories

Questions about PR Scope Responsibility

What does PR Scope Responsibility do?

Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points. PR Scope Responsibility is an agent skill from AliceJump/ok-end-field. Review or plan pull requests for responsibility boundaries, scope consistency, and minimal split points.

When should I use PR Scope Responsibility?

PR Scope Responsibility fits situations like: deciding whether a PR mixes independent reasons to change; whether diagnostics should be separated from core logic; whether the advertised PR scope matches the actual diff.

How do I install PR Scope Responsibility in Claude Code?

Run `npx skills add AliceJump/ok-end-field --skill pr-scope-responsibility -a claude-code`. Or copy the skill folder (.agents/skills/pr-scope-responsibility in AliceJump/ok-end-field) into .claude/skills/pr-scope-responsibility in your project. Claude Code loads it when a task matches its description.

How do I install PR Scope Responsibility in Codex?

Run `npx skills add AliceJump/ok-end-field --skill pr-scope-responsibility -a codex`. Or copy the skill folder (.agents/skills/pr-scope-responsibility in AliceJump/ok-end-field) into .agents/skills/pr-scope-responsibility in your project. Codex loads it when a task matches its description.

Can I use PR Scope Responsibility 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 AliceJump/ok-end-field --skill pr-scope-responsibility -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-scope-responsibility, .gemini/skills/pr-scope-responsibility, .github/skills/pr-scope-responsibility and .opencode/skills/pr-scope-responsibility in your project.

What does PR Scope Responsibility need to run?

SKILL.md names no scripts, command-line tools or credentials: PR Scope Responsibility is instructions for the agent only.

Does PR Scope Responsibility access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is PR Scope Responsibility 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 Scope Responsibility use?

PR Scope Responsibility is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Scope Responsibility use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Scope Responsibility?

Skills that share tags, products or a category with PR Scope Responsibility: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Scope Responsibility?

AliceJump (a GitHub user) maintains it in AliceJump/ok-end-field, which has 556 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.

Source: AliceJump/ok-end-field on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.