Agent skill

Choruz Pre Push Checks

Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full…

Apache-2.0Auto-check passedTesting & QA

Install Choruz Pre Push Checks

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a claude-code

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

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks --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/inclusionAI/Choruz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .claude/skills/choruz-pre-push-checks && 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/

Paste into Claude Code

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .claude/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .agents/skills/choruz-pre-push-checks && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .agents/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .cursor/skills/choruz-pre-push-checks && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .cursor/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/inclusionAI/Choruz.git --path .agents/skills/choruz-pre-push-checks

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .gemini/skills/choruz-pre-push-checks && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .gemini/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .github/skills/choruz-pre-push-checks && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .github/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install inclusionAI/Choruz choruz-pre-push-checks --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/choruz-pre-push-checks .opencode/skills/choruz-pre-push-checks && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "choruz-pre-push-checks" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-pre-push-checks into .opencode/skills/choruz-pre-push-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-pre-push-checks", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: choruz-pre-push-checks
GitHub stars: 1k
Token cost: ~1.4k tokens
SKILL.md length: 737 words
Files: 1
Skills in repo: 11
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full…

Works in 2 steps: Confirm the checkout and branch. → Print what CI will run for this diff and…
Testing & QA work in your project
SKILL.md covers Inspect the outgoing change, Select relevant evidence, Handle failures and Push procedure
Calls pnpm, cargo and bash

What it does

Choruz Pre Push Checks is an agent skill from inclusionAI/Choruz. Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full repository suite.

Its SKILL.md is about 1.4k 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 Testing & QA. The licence is Apache-2.0.

When your agent uses it

Testing & QA work in your project

Example prompts

“/choruz-pre-push-checks”

Requirements

Python 3

Workflow steps

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

Confirm the checkout and branch.
Print what CI will run for this diff and what to run first. The helper uses the workflow's own selector scripts, so its answer matches the…

What it can do on your machine

Read from SKILL.md and the folder at commit 7509c40. 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:
- pnpm
- cargo
- bash
- python3
- git
- vitest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and 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

Choruz Pre Push Checks loads about 1.4k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 737 words of instructions outside code blocks.

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

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 inclusionAI/Choruz at commit 7509c40, republished under its Apache-2.0 licence (© inclusionAI). 737 words, ~1,445 tokens.

Download SKILL.mdSave it as .claude/skills/choruz-pre-push-checks/SKILL.md (or your agent's skills folder).

name: choruz-pre-push-checks
description: Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full repository suite.

Choruz pre-push checks

When loaded from a personal skills directory, resolve repository links from this skill's canonical .agents/skills/choruz-pre-push-checks/ location in the active Choruz checkout, not from the installed copy.

Run relevant local evidence once before a push. There are no git hooks in this repository; CI owns exhaustive coverage, and it runs only what the changed paths need. A red job that could have been caught locally costs a CI round trip and a reviewer's trust.

Inspect the outgoing change

Confirm the checkout and branch.

git status --short --branch
git fetch -q origin main

Print what CI will run for this diff and what to run first. The helper uses the workflow's own selector scripts, so its answer matches the pull request's Detect changes job:

bash .agents/skills/choruz-pr/pr-plan.sh            # against origin/main
bash .agents/skills/choruz-pr/pr-plan.sh <base-ref>  # for a stacked branch

Select relevant evidence

Every behaviour change needs the narrowest available test that would fail for its regression; add broader checks only for surfaces the diff reaches. When the change adds or changes a resource-owning, parallel, or asynchronous test, apply choruz-ci-test-reliability first.

First map the outgoing scope to the policy's behaviour acceptance evidence. Inspect the selected assertions against that contract. pr-plan.sh and vitest related discover candidate checks, not proof of coverage: configuration, dynamic loading, subprocesses, cross-device dispatch and built artifacts can cross boundaries the import graph does not express. Explicitly select their owning scenarios and add missing tests; an empty selection is not passing evidence. Do not widen every change to the full suite or add --passWithNoTests to hide a missing owner.

Rust crate or service: cargo fmt --check, then cargo clippy -p <crate> --all-targets -- -D warnings and cargo test -p <crate> for the crate and its dependents (pr-plan.sh lists them). Integration tests that need PostgreSQL use infra/host/setup_test_database.sh.
Web source under apps/web: pnpm --dir apps/web exec vitest related --run <changed files> (the whole suite, pnpm web:test, only when the harness or a shared config changed), then pnpm web:check. Run pnpm web:build when next.config, app/ routing, or a dependency changed.
User-visible flow crossing server or runtime boundaries: the e2e spec that owns it, through the host stack: bash infra/host/web_e2e.sh tests/e2e/<feature>.spec.ts. A UI-only claim may use the policy's isolated component evidence. Use --repeat-each=3 when repairing a flake; repetition does not replace a deterministic assertion or negative control.
Migration or crates/choruz-application data path: the DB smoke, pnpm db:migration:smoke, and the API smoke, pnpm api:smoke. An applied migration is checksum-frozen (scripts/historical-migrations.sha256): never edit one, add a successor.
Agent Note, AGENTS.md, skill: python3 scripts/verify_agent_notes.py and python3 -m unittest discover scripts/tests.
CI workflow or selector script: python3 -m unittest discover .github/scripts/tests and a YAML parse of ci.yml; the pull request itself runs the full suite once, by design.
Contracts (openapi/): cargo test -p choruz-api-gateway contracts (the spec must list every registered route and nothing else).
Bridge, remote-control gateway, ops scripts: their build or lint (pnpm --dir services/choruz-bridge build, the gateway checks in ci.yml, pnpm ops:check).

Do not repeat a passing check merely because a commit or push follows. Do not run pnpm preflight:full by default; it is for an irreducibly repository-wide change or for diagnosing CI.

Show full SKILL.md (240 more words)Show less

Handle failures

If a relevant check fails, stop and fix or explain the blocker. Do not push and hope CI differs. "Flake" is not a root cause: a test that passes only when run alone is a defect in the test, and choruz-ci-test-reliability owns the fix. Never skip, disable, or quarantine a test to get green.

If a failure looks environment-specific, prove it: record the exact command, the failing test, and the platform-specific mismatch; confirm the non-platform evidence; prefer fixing the nondeterminism.

Push procedure

Run the selected checks once.
Commit with a Conventional Commits message; no model names or session identifiers beyond the trailers this repository already uses.
Push normally. Rewriting history is allowed only on a branch you created and never on someone else's; use --force-with-lease, never raw --force.
Verify the remote ref matches local HEAD, then watch the pull request checks: CI (linux) required is the one that gates the merge.

Report pending checks as pending. Inspect a failure before attributing it to the branch or the environment. If no check ever starts, read mergeStateStatus first: GitHub creates no pull_request run while a PR is conflicting, and resolving the conflict is the only fix.

At handoff, record the tested revision or dirty scope and the owning scenario's outcome, not just the command's exit status. Keep deterministic fixture results, live Harness results and manual visual observations separate; follow the policy when required evidence is unavailable.

Files

Just SKILL.md in .agents/skills/choruz-pre-push-checks of inclusionAI/Choruz.

Open the folder on GitHubat commit 7509c40

Compare with similar skills

Choruz Pre Push Checks 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.

Choruz Pre Push Checks compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Choruz Pre Push Checks this skillinclusionAI/Choruz	1k	—	~1.4k	Automated safety check: Pass	Apache-2.0	4 days ago
Web Application Testinganthropics/skills	180k	51 repos	~966	Automated safety check: Pass	Apache-2.0	yesterday
Diagnosing Bugsfossasia/eventyay-interpretation	1.6k	32 repos	~2.1k	Automated safety check: Pass	Apache-2.0	today
TDDpietheinstrengholt/rssmonster	564	30 repos	~906	Automated safety check: Pass	MIT	2 days ago
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph	112	11 repos	~2.4k	Automated safety check: Pass	None	8 mo ago
TDDsanity-io/sanity	6.4k	20 repos	~1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Web Application Testing
anthropics/skills
Official
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
180k GitHub starsUsed in 51 repos~966 tokens
Testing & QAAuto-check passed
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
1.6k GitHub starsUsed in 32 repos~2.1k tokens
Testing & QAAuto-check passed
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
564 GitHub starsUsed in 30 repos~906 tokens
Testing & QAAuto-check passed
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
112 GitHub starsUsed in 11 repos~2.4k tokens
Testing & QAAuto-check passed
TDD
sanity-io/sanity
Official
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
6.4k GitHub starsUsed in 20 repos~1k tokens
Testing & QAAuto-check passed
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
381 GitHub starsUsed in 9 repos~2.9k tokens
Testing & QAAuto-check passed

More from inclusionAI/Choruz

All 11 skills in this repo

Choruz Archive Agent Notes
inclusionAI/Choruz
A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, classifies implemented…
1k GitHub stars~1.2k tokensUpdated 4 days ago
Auto-check passed
Choruz Merging Stacked PRs
inclusionAI/Choruz
A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…
1k GitHub stars~866 tokensUpdated 4 days ago
Auto-check passed
Choruz CI Test Reliability
inclusionAI/Choruz
Design, review, and diagnose Choruz tests and fixtures that can fail nondeterministically under CI concurrency: parallel Playwright workers sharing one PostgreSQL and one API, vitest workers, cargo…
1k GitHub stars~1.8k tokensUpdated 4 days ago
Auto-check passed
Choruz Code Review
inclusionAI/Choruz
A skill your agent uses when reviewing a pull request in this repository; orients the reviewer to Choruz's standards (AGENTS.md conventions, the PR test policy, Agent Notes, the CI gates) and the…
1k GitHub stars~1.7k tokensUpdated 4 days ago
Auto-check passed
Choruz Doc
inclusionAI/Choruz
Create, restructure, review, audit, or migrate Choruz Markdown documentation (docs/, README, AGENTS.md, the in-app docs pages) using one owner per fact, tier placement, executed-operation…
1k GitHub stars~1.6k tokensUpdated 4 days ago
Auto-check passed
Choruz Find Simplifications
inclusionAI/Choruz
A skill your agent uses when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or…
1k GitHub stars~1.6k tokensUpdated 4 days ago
Auto-check passed

Questions about Choruz Pre Push Checks

What does Choruz Pre Push Checks do?

Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full…. Choruz Pre Push Checks is an agent skill from inclusionAI/Choruz. Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full repository suite.

When should I use Choruz Pre Push Checks?

Choruz Pre Push Checks fits situations like: testing & QA work in your project.

How do I install Choruz Pre Push Checks in Claude Code?

Run `npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a claude-code`. Or copy the skill folder (.agents/skills/choruz-pre-push-checks in inclusionAI/Choruz) into .claude/skills/choruz-pre-push-checks in your project. Claude Code loads it when a task matches its description.

How do I install Choruz Pre Push Checks in Codex?

Run `npx skills add inclusionAI/Choruz --skill choruz-pre-push-checks -a codex`. Or copy the skill folder (.agents/skills/choruz-pre-push-checks in inclusionAI/Choruz) into .agents/skills/choruz-pre-push-checks in your project. Codex loads it when a task matches its description.

Can I use Choruz Pre Push Checks 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 inclusionAI/Choruz --skill choruz-pre-push-checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/choruz-pre-push-checks, .gemini/skills/choruz-pre-push-checks, .github/skills/choruz-pre-push-checks and .opencode/skills/choruz-pre-push-checks in your project.

What does Choruz Pre Push Checks need to run?

Going by SKILL.md and its folder, Choruz Pre Push Checks needs the command-line tools its instructions call (pnpm, cargo, bash, python3, git and vitest). Our summary lists: Python 3.

Does Choruz Pre Push Checks 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 Choruz Pre Push Checks 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 Choruz Pre Push Checks use?

Choruz Pre Push Checks 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 Choruz Pre Push Checks use?

About 1.4k tokens (SKILL.md is roughly 5.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 Choruz Pre Push Checks?

Skills that share tags, products or a category with Choruz Pre Push Checks: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Choruz Pre Push Checks?

inclusionAI (a GitHub organization) maintains it in inclusionAI/Choruz, which has 1,017 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Choruz Pre Push Checks

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Choruz pre-push checks

Inspect the outgoing change

Select relevant evidence

Handle failures

Push procedure

Files

Compare with similar skills

Similar skills

More from inclusionAI/Choruz

Related

Questions about Choruz Pre Push Checks