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

Upstream PR Readiness

by InternationalColorConsortium in InternationalColorConsortium/iccDEV

Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request.

BSD-3-ClauseAuto-check passedDevelopment

Install Upstream PR Readiness

skills CLI
$ npx skills add InternationalColorConsortium/iccDEV --skill upstream-pr-readiness -a claude-code

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

GitHub CLI
$ gh skill install InternationalColorConsortium/iccDEV upstream-pr-readiness --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/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/upstream-pr-readiness .claude/skills/upstream-pr-readiness && 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
upstream-pr-readiness
GitHub stars
183
Token cost
~638 tokens
SKILL.md length
222 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request.

  • Works in 11 steps: Work in a clean clone or worktree. For… → Fetch the target branch and current base. → Rebase onto the current base before PR… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Hard Stop, Workflow, Result and References
  • Calls git, cmake and gh

What it does

Upstream PR Readiness is an agent skill from InternationalColorConsortium/iccDEV. Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request.

Its SKILL.md is about 640 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 and Authorization and RBAC. The repository describes itself as: iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color management profiles. The licence is BSD-3-Clause.

When your agent uses it

  • Tasks that involve Pull requests
  • Tasks that involve Authorization and RBAC

Example prompts

  • “/upstream-pr-readiness”

Requirements

  • Pre-approved tools (allowed-tools): bash, read, grep, glob, shell(git:*), shell(gh:*)

Workflow steps

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

  1. Work in a clean clone or worktree. For maintainer branch grooming, apply
  2. Fetch the target branch and current base.
  3. Rebase onto the current base before PR creation or review.
  4. Verify linear history and review the rewrite
  5. Review every changed file and confirm the PR description covers the entire
  6. Build normal targets and excluded regression helpers
  7. Record a base...HEAD contract matrix for every changed cross-cutting
  8. Run task-specific Release, compiler, sanitizer, diagnostics, runtime-dispatch,
  9. Remove generated artifacts and verify a clean worktree.
  10. Inspect all active and suppressed findings from review threads and review
  11. Produce the evidence record from

What it can do on your machine

Read from SKILL.md and the folder at commit 3c2425d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • bash
    • read
    • grep
    • glob
    • shell(git:*)
    • shell(gh:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cmake
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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

Upstream PR Readiness loads about 638 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 222 words of instructions outside code blocks.

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

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 InternationalColorConsortium/iccDEV at commit 3c2425d, republished under its BSD-3-Clause licence (© InternationalColorConsortium). 222 words, ~638 tokens.

Download SKILL.mdSave it as .claude/skills/upstream-pr-readiness/SKILL.md (or your agent's skills folder).
name
upstream-pr-readiness
description
Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request.
allowed-tools
bash, read, grep, glob, shell(git:*), shell(gh:*)

Upstream PR Readiness

Hard Stop

Find an exact user quotation authorizing PR creation or reopening. Requests to push, trigger CI, prepare a description, request review, or monitor checks do not qualify.

If explicit authorization is absent, return:

text
readiness: FAIL
reason: PR creation is not explicitly authorized

Do not call gh pr create, gh pr reopen, or an equivalent API.

Workflow

  1. Work in a clean clone or worktree. For maintainer branch grooming, apply ../../../docs/linear-stack-workflow.md local Git defaults first.

  2. Fetch the target branch and current base.

  3. Rebase onto the current base before PR creation or review.

  4. Verify linear history and review the rewrite:

    bash
    git config --get pull.rebase
git config --get merge.ff
git diff --check origin/master..HEAD
test -z "$(git rev-list --merges origin/master..HEAD)"
git range-diff origin/master origin/BRANCH HEAD

  5. Review every changed file and confirm the PR description covers the entire feature surface.

  6. Build normal targets and excluded regression helpers:

    bash
    cmake -S Build/Cmake -B /tmp/iccdev-pr-ready \
  -DCMAKE_BUILD_TYPE=Debug -DENABLE_TOOLS=ON
cmake --build /tmp/iccdev-pr-ready -j"$(nproc)"
cmake --build /tmp/iccdev-pr-ready \
  --target build-test-binaries -j"$(nproc)"
ctest --test-dir /tmp/iccdev-pr-ready --output-on-failure

  7. Record a base...HEAD contract matrix for every changed cross-cutting surface: producer, consumer, build/runtime behavior, platform or toolchain boundary, CI trigger, dependency owner, and local evidence.

  8. Run task-specific Release, compiler, sanitizer, diagnostics, runtime-dispatch, fallback, malformed-input, and other negative tests.

  9. Remove generated artifacts and verify a clean worktree.

  10. Inspect all active and suppressed findings from review threads and review summaries.

  11. Produce the evidence record from docs/governance/UPSTREAM_PR_READINESS.md.

Result

Only readiness: PASS plus explicit authorization permits PR creation.

If a re-review finds any new blocker, including one in the repair, change the result to FAIL and return to branch-only grooming.

References

  • ../../../docs/linear-stack-workflow.md

© InternationalColorConsortium, BSD-3-Clause. 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 .github/skills/upstream-pr-readiness of InternationalColorConsortium/iccDEV.

Open the folder on GitHubat commit 3c2425d

Compare with similar skills

Upstream PR Readiness 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.

Upstream PR Readiness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Upstream PR Readiness this skillInternationalColorConsortium/iccDEV183—~638Automated safety check: PassBSD-3-Clause
Project Pull Requestswimmwatch/cloakbrowser-mcp164—~1kAutomated safety check: PassMIT
Code ReviewAzure/sap-automation146—~7kAutomated safety check: PassMIT
Code Review SecurityOWASP/secure-agent-playbook188—~549Automated safety check: PassCC-BY-4.0
Stewardrichlander/dotnet-inspect151—~1.7kAutomated safety check: PassNone
Security Architecture Reviewcbrock84/headcount2k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    164 GitHub stars~1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Code Review

    Azure/sap-automation

    Official

    Review pull requests in the SAP Deployment Automation Framework.

    146 GitHub stars~7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Code Review Security

    OWASP/secure-agent-playbook

    Security-focused code review mapped to OWASP Top 10 and ASVS.

    188 GitHub stars~549 tokensUpdated 16 days ago
    DevelopmentAuto-check passed

  • Steward

    richlander/dotnet-inspect

    A skill your agent uses when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event.

    151 GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Security Architecture Review

    cbrock84/headcount

    Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    SecurityAuto-check passed

  • 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

More from InternationalColorConsortium/iccDEV

All 23 skills in this repo

  • Afl Smoke

    InternationalColorConsortium/iccDEV

    Run or update the iccDEV AFL++ manual smoke workflow, seeds, and maintainer documentation.

    183 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Avx2 Clut Diagnostics

    InternationalColorConsortium/iccDEV

    Diagnose runtime-dispatched AVX2 3D CLUT interpolation, collect trace evidence, validate vector and masked-tail output, and prepare optimization handoff data.

    183 GitHub stars~850 tokensUpdated yesterday
    Auto-check passed

  • Clusterfuzzlite

    InternationalColorConsortium/iccDEV

    Build, test, or update the iccDEV ClusterFuzzLite libFuzzer integration across ASan, UBSan, and MSan.

    183 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • iOS Clut Editor

    InternationalColorConsortium/iccDEV

    Build, review, and maintain the ios-clut-editor profile and 3D CLUT editing proof-of-concept app without repeating prior iOS review-loop failures.

    183 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • iOS Manual Examples

    InternationalColorConsortium/iccDEV

    Maintain the manual iOS example app CMake projects, local Xcode build helpers, device signing guard rails, and documentation.

    183 GitHub stars~796 tokensUpdated yesterday
    Auto-check passed

  • JSON Config Regression

    InternationalColorConsortium/iccDEV

    Validate iccDEV JSON/profile config parser changes with fail-closed regression gates and CLI exercises.

    183 GitHub stars~469 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Upstream PR Readiness

What does Upstream PR Readiness do?

Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request. Upstream PR Readiness is an agent skill from InternationalColorConsortium/iccDEV. Verify explicit authorization and complete grooming before creating, reopening, or requesting review on an upstream pull request.

When should I use Upstream PR Readiness?

Upstream PR Readiness fits situations like: tasks that involve Pull requests; tasks that involve Authorization and RBAC.

How do I install Upstream PR Readiness in Claude Code?

Run `npx skills add InternationalColorConsortium/iccDEV --skill upstream-pr-readiness -a claude-code`. Or copy the skill folder (.github/skills/upstream-pr-readiness in InternationalColorConsortium/iccDEV) into .claude/skills/upstream-pr-readiness in your project. Claude Code loads it when a task matches its description.

How do I install Upstream PR Readiness in Codex?

Run `npx skills add InternationalColorConsortium/iccDEV --skill upstream-pr-readiness -a codex`. Or copy the skill folder (.github/skills/upstream-pr-readiness in InternationalColorConsortium/iccDEV) into .agents/skills/upstream-pr-readiness in your project. Codex loads it when a task matches its description.

Can I use Upstream PR Readiness 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 InternationalColorConsortium/iccDEV --skill upstream-pr-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upstream-pr-readiness, .gemini/skills/upstream-pr-readiness, .github/skills/upstream-pr-readiness and .opencode/skills/upstream-pr-readiness in your project.

What does Upstream PR Readiness need to run?

Going by SKILL.md and its folder, Upstream PR Readiness needs the command-line tools its instructions call (git, cmake and gh). Its frontmatter pre-approves these tools: bash, read, grep, glob, shell(git:*), shell(gh:*).

Does Upstream PR Readiness access the network?

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

Is Upstream PR Readiness 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 Upstream PR Readiness use?

Upstream PR Readiness is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Upstream PR Readiness use?

About 638 tokens (SKILL.md is roughly 2.6k 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 Upstream PR Readiness?

Skills that share tags, products or a category with Upstream PR Readiness: Project Pull Request (swimmwatch/cloakbrowser-mcp, 164 stars), Code Review (Azure/sap-automation, 146 stars), Code Review Security (OWASP/secure-agent-playbook, 188 stars) and Steward (richlander/dotnet-inspect, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Upstream PR Readiness?

InternationalColorConsortium (a GitHub organization) maintains it in InternationalColorConsortium/iccDEV, which has 183 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 9, 2026.

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