What is pre-submit-pr?

A pre-submission checklist for pull requests, which are requests to merge code changes into a shared project. It checks branch freshness, code style, tests, debugging code, project rules, API changes, and documentation.

Use it before creating or updating a pull request, pushing for review, or checking whether a change is ready.

It helps catch problems before reviewers see the change or the pull request is opened. It also flags changes that may need a design review or formal proposal.

pre-submit-pr — Skill by huggingface

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/huggingface/openenv/pre-submit-pr

Any agent

npx skills add huggingface/OpenEnv --skill pre-submit-pr

Clone the repo

git clone --depth 1 https://github.com/huggingface/OpenEnv

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 968 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00048	$0.00968
Opus 5	$0.00024	$0.00484
Sonnet 5	$0.00010	$0.00194
Haiku 4.5	$0.00005	$0.00097

Measured 2d ago against content hash c58757ea231e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pre-submit-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/pre-submit-pr/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre-Submit PR Check

Comprehensive validation before submitting a pull request. Run this before creating or updating a PR.

Instructions

Check branch freshness (BLOCKING):
- Run git fetch origin main to get latest main
- Run git rev-list --count HEAD..origin/main to check commits behind
- If > 0 commits behind, merge main before proceeding: git merge origin/main
- This prevents "branch out of date" issues on GitHub
Run all automated hooks:
- bash .claude/hooks/lint.sh - format check (includes ruff format + ruff check)
- bash .claude/hooks/test.sh - run tests
- bash .claude/hooks/check-debug.sh - find debug code
Run alignment review:
- Read .claude/docs/PRINCIPLES.md and .claude/docs/INVARIANTS.md
- Compare changes against principles and invariants
- Identify Tier 1 (mechanical) and Tier 2 (alignment) issues
RFC check:
- If changes touch src/openenv/core/, flag for RFC consideration
- If any public API signatures change, RFC required
- Check against existing RFCs in rfcs/ for conflicts
Documentation freshness check:
- Review .claude/docs/REPO_WALKTHROUGH.md against the current repo structure
- If the PR adds new directories, moves files, or changes structure significantly:
  - Update REPO_WALKTHROUGH.md to reflect the changes
  - Include these updates in the PR
- Check triggers: new directories in src/, envs/, .claude/, or rfcs/
- Check if any public API signatures changed (function/class renames, new params):
  - Search for references in docs/, examples/, README.md, other .py docstrings
  - If stale references found, recommend running /update-docs before PR
Summarize PR readiness:
- List all blocking issues
- List all discussion points for reviewers
- Provide overall verdict
After push/PR creation, run the post-push check:
- bash .claude/hooks/post-push-pr.sh
- Verifies: PR is open, no merge conflicts, branch freshness, PR description quality, CI check status

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 112 lines · 48 tokens per session scan A c58757ea231e

Subscribe to this mod's changes

pre-submit-pr is a skill published in the GitHub repository huggingface/OpenEnv (2,531 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 968 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Git and workflow

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens