New: 97,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

Pull Requests

by lightly-ai in lightly-ai/lightly-studio

Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review.

Apache-2.0Auto-check passedDevelopment

Install Pull Requests

skills CLI
$ npx skills add lightly-ai/lightly-studio --skill pull-requests -a claude-code

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

GitHub CLI
$ gh skill install lightly-ai/lightly-studio pull-requests --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/lightly-ai/lightly-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pull-requests .claude/skills/pull-requests && 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
pull-requests
GitHub stars
896
Token cost
~709 tokens
SKILL.md length
399 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review.

  • Works in 4 steps: Keep PRs Small → One Purpose Per PR → Every PR Must Be Reviewable on Its Own → …
  • Tasks that involve Pull requests
  • SKILL.md covers Guidelines and Exceptions
  • Calls git

What it does

Pull Requests is an agent skill from lightly-ai/lightly-studio. Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review. Covers the size targets, the one-purpose-per-PR rule, what makes a PR reviewable on its own, and the exceptions for dependency bumps, codemods, migrations, and generated files.

Its SKILL.md is about 710 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: LightlyStudio - The Unified Data Platform for Multimodal ML. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/pull-requests”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Keep PRs Small
  2. One Purpose Per PR
  3. Every PR Must Be Reviewable on Its Own
  4. Description & Suggested Reviewers

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Pull Requests loads about 709 tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 399 words of instructions outside code blocks.

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

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 lightly-ai/lightly-studio at commit 66da613, republished under its Apache-2.0 licence (© lightly-ai). 399 words, ~709 tokens.

Download SKILL.mdSave it as .claude/skills/pull-requests/SKILL.md (or your agent's skills folder).
name
pull-requests
description
Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review. Covers the size targets, the one-purpose-per-PR rule, what makes a PR reviewable on its own, and the exceptions for dependency bumps, codemods, migrations, and generated files.

Pull Request Guidelines

Break changes down into small, focused pull requests that can be easily reviewed. As a rule of thumb, a PR should be reviewable in under 15 minutes.

Guidelines

1. Keep PRs Small
  • Ideal PR size is under 100 changed lines. Under 200 lines is usually acceptable. Larger changes should be split into multiple PRs unless there is a reason not to.
  • It is okay to have a larger PR if it is mostly mechanical changes, such as generated files, test data, or formatting. But the core PR logic should ideally remain under 100 lines.
  • Use stacked PRs to work on larger features without being blocked by review.
2. One Purpose Per PR
  • A pull request should do one thing only. Do not mix unrelated changes in the same PR.
  • Minor improvements to the neighborhood of the main change are ok, but larger refactors should be in a separate PR.
3. Every PR Must Be Reviewable on Its Own

A reviewer should be able to understand what changed, why, and how it was validated. That usually means:

  • In the code
    • clear comments for non-obvious logic
    • TODO comments for future work
    • tests for new behavior when appropriate
    • updated docs when user-facing behavior changed
    • no unrelated formatting or cleanup noise
  • In the PR on GitHub
    • clear PR description
    • screenshots or recordings for UI changes
    • line comments for non-obvious code changes

In some cases, the tests or a docs change may be in a separate PR if it would be too large to review together.

Show full SKILL.md (145 more words)Show less
4. Description & Suggested Reviewers
  • Follow .github/pull_request_template.md. Keep the description short and human readable.
  • Propose a few short bullet points that say which problem the PR addresses and how it is solved. Write them so that a reader who does not know the code can follow.
  • Assign the reviewer most likely to help, based on git blame/git log history of the touched files or lines, and recommend an alternative one at the end of the description.
  • For a stack of PRs, prefer the same reviewer(s) for each item in the stack, unless the items can be reviewed independently.

Exceptions

Some PRs will not fit the normal shape. Examples:

  • dependency upgrades
  • mechanical codemods
  • large test updates
  • schema or migration changes
  • generated files

In those cases, optimize for reviewer clarity:

  • explain why the PR is large
  • separate mechanical and logical changes where possible
  • call out risk areas explicitly

© lightly-ai, Apache-2.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/pull-requests of lightly-ai/lightly-studio.

Open the folder on GitHubat commit 66da613

Compare with similar skills

Pull Requests 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.

Pull Requests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pull Requests this skilllightly-ai/lightly-studio896—~709Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 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
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

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.

    296k 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

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k 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

More from lightly-ai/lightly-studio

  • Backend Guide

    lightly-ai/lightly-studio

    Read before adding or changing backend code in lightlystudio - FastAPI routes, services, resolvers, SQLModel tables, or database access.

    896 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Frontend Guide

    lightly-ai/lightly-studio

    Read before writing or reviewing any frontend code in lightlystudioview - Svelte, TypeScript, or SvelteKit files.

    896 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Python Guide

    lightly-ai/lightly-studio

    Read before writing or reviewing any Python code in this repository.

    896 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Glossary

    lightly-ai/lightly-studio

    Read when naming anything user-facing - GUI text, docs, public Python API names, arguments, docstrings, or error messages.

    896 GitHub stars~482 tokensUpdated today
    Auto-check passed

  • Best Practices

    lightly-ai/lightly-studio

    Read when adding a new function, module, or component, or when a file is growing large enough that splitting it is worth considering.

    896 GitHub stars~424 tokensUpdated today
    Auto-check passed

Categories

Questions about Pull Requests

What does Pull Requests do?

Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review. Pull Requests is an agent skill from lightly-ai/lightly-studio. Read when opening a pull request, writing a PR description, splitting work into PRs, or deciding whether a change is too large to review.

When should I use Pull Requests?

Pull Requests fits situations like: tasks that involve Pull requests.

How do I install Pull Requests in Claude Code?

Run `npx skills add lightly-ai/lightly-studio --skill pull-requests -a claude-code`. Or copy the skill folder (.agents/skills/pull-requests in lightly-ai/lightly-studio) into .claude/skills/pull-requests in your project. Claude Code loads it when a task matches its description.

How do I install Pull Requests in Codex?

Run `npx skills add lightly-ai/lightly-studio --skill pull-requests -a codex`. Or copy the skill folder (.agents/skills/pull-requests in lightly-ai/lightly-studio) into .agents/skills/pull-requests in your project. Codex loads it when a task matches its description.

Can I use Pull Requests 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 lightly-ai/lightly-studio --skill pull-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pull-requests, .gemini/skills/pull-requests, .github/skills/pull-requests and .opencode/skills/pull-requests in your project.

What does Pull Requests need to run?

Going by SKILL.md and its folder, Pull Requests needs the command-line tools its instructions call (git).

Does Pull Requests access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pull Requests 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 Pull Requests use?

Pull Requests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pull Requests use?

About 709 tokens (SKILL.md is roughly 2.8k 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 Pull Requests?

Skills that share tags, products or a category with Pull Requests: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pull Requests?

lightly-ai (a GitHub organization) maintains it in lightly-ai/lightly-studio, which has 896 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: lightly-ai/lightly-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.