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

Choruz Pre Simplify Audit

by inclusionAI in inclusionAI/Choruz

Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness.

Apache-2.0Auto-check passedDevelopment

Install Choruz Pre Simplify Audit

skills CLI
$ npx skills add inclusionAI/Choruz --skill choruz-pre-simplify-audit -a claude-code

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

GitHub CLI
$ gh skill install inclusionAI/Choruz choruz-pre-simplify-audit --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-simplify-audit .claude/skills/choruz-pre-simplify-audit && 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
choruz-pre-simplify-audit
GitHub stars
1k
Token cost
~1.9k tokens
SKILL.md length
967 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness.

  • Works in 3 steps: Requirements were executed → The change does not create structural debt → Tests can detect the claimed failure
  • Development work in your project
  • SKILL.md covers Establish the reviewed scope, Three audit lenses and Verdict and re-audit
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Choruz Pre Simplify Audit is an agent skill from inclusionAI/Choruz. Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness. Read-only and limited to the proposed change and its affected paths; not an implementation task or repository-wide cleanup.

Its SKILL.md is about 1.9k 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. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/choruz-pre-simplify-audit”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Requirements were executed
  2. The change does not create structural debt
  3. Tests can detect the claimed failure

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 Simplify Audit loads about 1.9k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 967 words of instructions outside code blocks.

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

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). 967 words, ~1,857 tokens.

Download SKILL.mdSave it as .claude/skills/choruz-pre-simplify-audit/SKILL.md (or your agent's skills folder).
name
choruz-pre-simplify-audit
description
Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness. Read-only and limited to the proposed change and its affected paths; not an implementation task or repository-wide cleanup.

Independent pre-simplify audit

When installed personally, resolve repository links from the canonical .agents/skills/choruz-pre-simplify-audit/ in the active Choruz checkout.

choruz-pr owns delegation and the remediation loop: an independent GPT-5.6 Terra agent (gpt-5.6-terra) performs the first audit and every re-audit before simplify. This skill owns the audit criteria. Do not implement fixes, edit files, push, merge or recursively delegate. The audit does not replace simplify, behavioural tests or final CI.

Establish the reviewed scope

Obtain the user request and constraints, base/head revisions, proposed diff including relevant uncommitted and untracked files, execution evidence and prior findings. Record a reproducible diff identity: revisions plus a patch digest or artifact identifying any uncommitted content. Never include secrets.

Read the applicable AGENTS.md, test policy and the current PR workflow stage. Independently identify relevant skills from the task and diff; the author's list is not authoritative. Read each selected skill fully and its required references. Follow affected callers and owners, including relevant architecture and Agent Notes, rather than scanning the whole repository. Referenced workflows supply criteria, not permission for this read-only auditor to implement, publish or start another audit.

Use supplied logs and artifacts and safe read-only inspection. If reproduction requires test setup, credential use, database writes or other state changes, request scoped execution evidence from the implementer instead. Do not invent execution evidence or broaden the user's authorization.

Three audit lenses

1. Requirements were executed

Map applicable requirements to evidence, not to declarations that a skill was read. A planned command, test filename, checklist tick or author assurance is not an observed result. Check the command, outcome, tested revision and artifact agree with the claim.

Classify each relevant requirement as verified, missing/unverified, not applicable with a scope reason, or due later with the named workflow step. Only due-now requirements gate pre-simplify: step 2 behavioural evidence is due, but simplify itself, final selected checks, PR labels and merge cleanup are later. Do not require all skills or the full suite to fill a table.

2. The change does not create structural debt

For structural candidates, use the consumer-evidence criteria in choruz-find-simplifications. Look for duplicate implementations of one contract, parallel sources of truth, mixed responsibilities, bypassed shared owners, speculative abstractions and obsolete fallback or compatibility paths left alongside the new path.

Trace production consumers before calling code dead, including runtime dispatch, configuration, scripts and persisted formats. Distinguish intentional harness/transport differences from accidental duplication. Show the concrete maintenance or correctness risk and a bounded correction, not just a preferred style. File size, abstraction count or the word "legacy" alone is not a finding.

Block introduced or worsened structural defects and affected violations of repository contracts. Unrelated pre-existing debt and optional improvements are advisory; do not demand a whole-repository rewrite or a quota of findings. Similar names or the coexistence of two paths do not prove duplicate ownership. Without caller/owner evidence, report the structural concern as unverified, not as a demonstrated defect; explain which evidence would decide it.

Show full SKILL.md (479 more words)Show less
3. Tests can detect the claimed failure

Apply the test policy's behaviour acceptance evidence to the affected contract. Inspect assertions and fixtures, then ask which plausible broken implementation would still pass. A boolean type check, mock call count, nonempty output or snapshot update alone cannot establish a user-visible outcome.

Check the required production entry path and owner-side result: for example, a click that reports success must reach the intended device and leave the expected persisted result. Replacing the very route, binding or storage under test with a success mock does not prove that boundary. Mock unrelated expensive dependencies only when the remaining claim is honest.

For bug fixes and new guards, verify the policy-required focused negative control and passing result, not just a green run. Check ordinary affected lifecycle and recovery scenarios; do not impose every device/harness combination or speculative edge case. Read choruz-ci-test-reliability when changed tests involve shared state, concurrency, clocks, ports or asynchronous cleanup.

Match the evidence to the surface: pure prose does not need a product e2e; behavioural skill changes need a scoped decision example; visual claims need visual evidence where required. Code inspection is not a real runtime test, and green CI does not prove assertions are meaningful. Report unavailable required evidence as unverified, never as a successful fallback.

Apply test value and incremental cost to changed tests and their nearest overlapping scenarios. Check the existing owner, the new distinguishing guarantee, false-green exits, obsolete coverage and justified execution cost. Block introduced or worsened defects; keep unrelated existing debt advisory. Do not demand extra tests or deletions merely to satisfy a count. CI-selector changes require checking overlap and distinct environments, not assuming full and selected jobs are interchangeable.

Verdict and re-audit

Return a compact report containing:

  • Reviewed scope identity and evidence references.
  • Relevant requirements, their source, evidence and status across all three lenses.
  • Stable finding IDs, blocking/advisory status, precise location, concrete consequence, evidence and the minimum correction or verification needed.
  • Verdict: PASS when all due-now obligations are verified; FAIL for a demonstrated due-now blocker; UNVERIFIED when required evidence or access is missing. A FAIL may also contain unverified obligations.

Advisory findings and explicitly deferred later steps do not prevent PASS. Record any explicit user-approved scope reduction or evidence exemption with its source; it does not turn an untested claim into a verified one. An author's request to waive their own missing evidence is not a user exemption.

On re-audit, inspect the updated diff and evidence, revisit every previous blocker and check affected new changes. Accept a reasoned rebuttal when supported by evidence. Close a finding only after independently verifying the correction or that it was inapplicable; retain unresolved IDs. An author's "fixed" message is not closure. Only an explicit auditor PASS lets the PR workflow proceed. A later change that invalidates the reviewed evidence requires a scoped re-audit; an old verdict cannot certify a new diff.

© inclusionAI, Apache-2.0. 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 .agents/skills/choruz-pre-simplify-audit of inclusionAI/Choruz.

Open the folder on GitHubat commit 7509c40

Compare with similar skills

Choruz Pre Simplify Audit 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 Simplify Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Choruz Pre Simplify Audit this skillinclusionAI/Choruz1k—~1.9kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-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

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-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 3 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 3 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 3 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 3 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 3 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 3 days ago
    Auto-check passed

Categories

Questions about Choruz Pre Simplify Audit

What does Choruz Pre Simplify Audit do?

Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness. Choruz Pre Simplify Audit is an agent skill from inclusionAI/Choruz. Perform the independent Choruz pre-simplify audit or re-audit of skill execution evidence, code structure and test effectiveness.

When should I use Choruz Pre Simplify Audit?

Choruz Pre Simplify Audit fits situations like: development work in your project.

How do I install Choruz Pre Simplify Audit in Claude Code?

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

How do I install Choruz Pre Simplify Audit in Codex?

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

Can I use Choruz Pre Simplify Audit 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-simplify-audit -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-simplify-audit, .gemini/skills/choruz-pre-simplify-audit, .github/skills/choruz-pre-simplify-audit and .opencode/skills/choruz-pre-simplify-audit in your project.

What does Choruz Pre Simplify Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Choruz Pre Simplify Audit is instructions for the agent only.

Does Choruz Pre Simplify Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Choruz Pre Simplify Audit 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 Simplify Audit use?

Choruz Pre Simplify Audit 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 Simplify Audit use?

About 1.9k tokens (SKILL.md is roughly 7.4k 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 Simplify Audit?

Skills that share tags, products or a category with Choruz Pre Simplify Audit: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Choruz Pre Simplify Audit?

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.