OpenParable
Skip to content
← Back to skills

Rabby Yarn V4 Commit Check

DevOps & Security
rabby-yarn-v4-commit-check

Rabby Yarn V4 Commit Check is an Agent Skill for devops & security published in the RabbyHub/Rabby repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use in the Rabby repository on Yarn v4 branches before creating, amending, merging, or pushing commits. Requires running yarn and yarn check from the repository root before committing, and blocks commits when either command fails.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/RabbyHub/Rabby/blob/HEAD/skills/rabby-yarn-v4-commit-check/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rabby-yarn-v4-commit-check, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Rabby Yarn v4 Commit Check

Use this workflow whenever a task in the Rabby repository will create a commit, amend a commit, create a merge commit, or push a branch that should already include committed work.

Required Check

Before running git commit, git commit --amend, or completing a merge commit, run these commands from the repository root:

yarn
yarn check

Treat the sequence as yarn && yarn check: only run yarn check after yarn exits successfully.

Commit Rules

  • Do not commit if yarn or yarn check exits non-zero.
  • If yarn changes tracked dependency files, inspect the diff and include only intentional changes.
  • If the failure appears unrelated to the current edit, report the exact failing command and the relevant error output before deciding whether to proceed.
  • Do not substitute npm install, npm run check, yarn lint, or yarn typecheck for the required sequence unless the user explicitly redirects the workflow.
  • After committing or pushing, report the commit hash and the validation commands that passed.