How do I install the Rpce Contribution Check skill?

Run npx skillmds@latest add repoprompt/rpce-contribution-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rpce Contribution Check safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rpce Contribution Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rpce Contribution Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rpce Contribution Check?

repoprompt (@repoprompt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rpce Contribution Check by repoprompt

Name: Rpce Contribution Check
Rating: 4.666666666666667 (3 reviews)
Author: repoprompt

Rpce Contribution Check

Validate RepoPrompt CE contributions before committing or pushing. Use whenever an agent is about to create a commit, push the current branch, rewrite history, delete a branch or fork, or change GitHub-visible repository state. Enforces staged-index and outgoing-range secret scanning, repository guardrails, clean push boundaries, an explicit PR-ready lane for path-selected heavyweight validation, and explicit approval for destructive Git or visible live-app operations.

repoprompt Updated Sep 22, 2026

File contents

RepoPrompt CE Contribution Check

Run the repository-local safety preflight before every commit and push. Read AGENTS.md first and use daemon-coordinated validation where available. Use the explicit pr-ready lane when computed-outgoing-range path-selected local validation evidence is required.

Before committing

Review git status --short and inspect the intended diff.
Stage only intended files. Review git diff --cached --stat and git diff --cached.
Run:

.agents/skills/rpce-contribution-check/scripts/preflight.sh commit

Rerun commit preflight after any staging change, including partial-staging updates. Commit mode scans materialized staged index blobs, not merely working-tree copies.
Keep secret values redacted in terminal output and summaries.

Before pushing

Ensure the working tree is clean.
Run the immediate push safety gate:

.agents/skills/rpce-contribution-check/scripts/preflight.sh push

Review the computed current-branch range printed by the script.
Read references/validation-matrix.md and ensure any required focused, release, smoke, or PR-ready evidence is recorded before pushing.
Push only the intended current branch and check the GitHub Actions run after pushing.

Default push mode validates whitespace, staged-index secrets, guardrails, clean worktree state, the current-branch outgoing range, and outgoing-range secrets. It does not run heavyweight lint/test/build/provider lanes.

Push mode validates only the current branch against its configured upstream. For a non-main topic branch without a configured upstream, it may use origin/main as an explicit comparison fallback. It does not validate tags, --all, --mirror, or arbitrary refspecs.

Full / PR-ready local validation

When preparing computed-outgoing-range local PR evidence, when a maintainer requests it, or when the validation matrix calls for the path-selected lane, run:

.agents/skills/rpce-contribution-check/scripts/preflight.sh pr-ready

pr-ready reruns the push safety gate, then runs any matching path-selected heavyweight lanes for the computed outgoing range, such as conductor selftests, Swift lint, root/provider tests, product builds, and generated Xcode workspace validation for Xcode boundary changes. Heavy build/test/package lanes may wait on conductor's per-user global heavy slot when another worktree is already running Swift/Xcode-heavy work; treat that as coordination, not a reason to launch duplicate direct swift/xcodebuild commands. It does not replace explicit release validation, live smoke, already-pushed PR-base comparison, or destructive-operation approval requirements.

Escalate before destructive operations

Obtain explicit user approval immediately before force-push, history rewrite, branch deletion, fork deletion, credential rotation, any other GitHub-visible destructive mutation, visible app launch/relaunch, or stopping a visible app. Do not bundle approval for a future destructive step into an earlier request.

Focused validation

Read references/validation-matrix.md when deciding whether additional focused tests, builds, PR-ready validation, release checks, or live smoke are required.

---name: rpce-contribution-checkdescription: Validate RepoPrompt CE contributions before committing or pushing. Use whenever an agent is about to create a commit, push the current branch, rewrite history, delete a branch or fork, or change GitHub-visible repository state. Enforces staged-index and outgoing-range secret scanning, repository guardrails, clean push boundaries, an explicit PR-ready lane for path-selected heavyweight validation, and explicit approval for destructive Git or visible live-app operations.---# RepoPrompt CE Contribution CheckRun the repository-local safety preflight before every commit and push. Read `AGENTS.md` first and use daemon-coordinated validation where available. Use the explicit `pr-ready` lane when computed-outgoing-range path-selected local validation evidence is required.## Before committing1. Review `git status --short` and inspect the intended diff.2. Stage only intended files. Review `git diff --cached --stat` and `git diff --cached`.3. Run:```bash.agents/skills/rpce-contribution-check/scripts/preflight.sh commit```4. Rerun commit preflight after any staging change, including partial-staging updates. Commit mode scans materialized staged index blobs, not merely working-tree copies.5. Keep secret values redacted in terminal output and summaries.## Before pushing1. Ensure the working tree is clean.2. Run the immediate push safety gate:```bash.agents/skills/rpce-contribution-check/scripts/preflight.sh push```3. Review the computed current-branch range printed by the script.4. Read [references/validation-matrix.md](references/validation-matrix.md) and ensure any required focused, release, smoke, or PR-ready evidence is recorded before pushing.5. Push only the intended current branch and check the GitHub Actions run after pushing.Default push mode validates whitespace, staged-index secrets, guardrails, clean worktree state, the current-branch outgoing range, and outgoing-range secrets. It does not run heavyweight lint/test/build/provider lanes.Push mode validates only the current branch against its configured upstream. For a non-`main` topic branch without a configured upstream, it may use `origin/main` as an explicit comparison fallback. It does not validate tags, `--all`, `--mirror`, or arbitrary refspecs.## Full / PR-ready local validationWhen preparing computed-outgoing-range local PR evidence, when a maintainer requests it, or when the validation matrix calls for the path-selected lane, run:```bash.agents/skills/rpce-contribution-check/scripts/preflight.sh pr-ready````pr-ready` reruns the push safety gate, then runs any matching path-selected heavyweight lanes for the computed outgoing range, such as conductor selftests, Swift lint, root/provider tests, product builds, and generated Xcode workspace validation for Xcode boundary changes. Heavy build/test/package lanes may wait on conductor's per-user global heavy slot when another worktree is already running Swift/Xcode-heavy work; treat that as coordination, not a reason to launch duplicate direct `swift`/`xcodebuild` commands. It does not replace explicit release validation, live smoke, already-pushed PR-base comparison, or destructive-operation approval requirements.## Escalate before destructive operationsObtain explicit user approval immediately before force-push, history rewrite, branch deletion, fork deletion, credential rotation, any other GitHub-visible destructive mutation, visible app launch/relaunch, or stopping a visible app. Do not bundle approval for a future destructive step into an earlier request.## Focused validationRead [references/validation-matrix.md](references/validation-matrix.md) when deciding whether additional focused tests, builds, PR-ready validation, release checks, or live smoke are required.

Frequently asked questions