Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
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…
Install Choruz Find Simplifications
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inclusionAI/Choruz choruz-find-simplifications --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .claude/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.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/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .claude/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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 install https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplificationsType 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.
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inclusionAI/Choruz choruz-find-simplifications --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .agents/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .agents/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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.
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inclusionAI/Choruz choruz-find-simplifications --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .cursor/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .cursor/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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 https://github.com/inclusionAI/Choruz.git --path .agents/skills/choruz-find-simplifications--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inclusionAI/Choruz choruz-find-simplifications --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .gemini/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.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/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .gemini/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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.
$ gh skill install inclusionAI/Choruz choruz-find-simplificationsInstalls 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).
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .github/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.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/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .github/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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.
$ npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inclusionAI/Choruz choruz-find-simplifications --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/choruz-find-simplifications .opencode/skills/choruz-find-simplifications && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "choruz-find-simplifications" agent skill from https://github.com/inclusionAI/Choruz/tree/main/.agents/skills/choruz-find-simplifications into .opencode/skills/choruz-find-simplifications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choruz-find-simplifications", 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-find-simplifications- GitHub stars
- 1k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 819 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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…
- Working in this repository to find non-obvious simplification candidates
- SKILL.md covers Start with repository context, What counts as a strong…, Survey broadly and Prove or reject each candidate, plus 5 more sections
- Calls git and python3
- Remove redundant comments
What it does
Choruz Find Simplifications is an agent skill from inclusionAI/Choruz. Use when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another branch; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-crate-exists surfaces.
Its SKILL.md is about 1.6k 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
- Working in this repository to find non-obvious simplification candidates
- Remove redundant comments
- Implementation-heavy documentation
- Write proposed Agent Notes
Example prompts
- “/choruz-find-simplifications”
Requirements
- Python 3
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:
gitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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 Find Simplifications loads about 1.6k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 819 words of instructions outside code blocks.
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). 819 words, ~1,608 tokens.
Download SKILL.mdSave it as
.claude/skills/choruz-find-simplifications/SKILL.md (or your agent's skills folder).- name
- choruz-find-simplifications
- description
- Use when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another branch; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-crate-exists surfaces.
Finding Choruz simplifications
Turn a broad "find things to simplify" request into evidence-backed Agent Notes that remove or collapse existing surface area. This is guidance, not a checklist: follow the code, keep judgement active, and prefer a few well-proven candidates over a pile of thin guesses.
Start with repository context
- Read AGENTS.md, especially the pre-release stance: no compatibility shims, delete the old path.
- Skim docs/architecture.md before judging anything under
crates/,services/orservices/choruz-pipeline; a simplification that fights the stage model (router, executor, writer, fanout) or the sync feed needs extra evidence. - Use the Agent Note tree to learn intentional architecture. A recorded decision is not a veto, but a candidate that collapses one must beat its recorded rationale, not just cite this skill.
- Treat the multiple terminal drivers (Claude Code, Codex, Gemini) and the connector, bridge and remote-control transports as intentional by default; removing an unused method inside one of them can still be valid.
What counts as a strong candidate
- A handler, endpoint, event, config knob, helper, crate, table column or test fixture has no production consumer.
- Tests or docs are the only consumers, and the behaviour they pin is not load-bearing.
- Two representations mirror the same fact (a cached count and its source rows, a client-side copy of server state that the sync feed already carries).
- A shared crate exposes methods every service must support but no service calls.
- A feature implements speculative product generality with no owner.
- A hand-rolled parser, retry loop, path matcher or serializer duplicates a maintained crate or npm package the workspace already depends on, and the swap would delete the implementation plus its dedicated tests.
- Dead paths left by a retired surface (the desktop app, the maildir protocol's predecessors, renamed features) that still compile because nothing removed them.
Thin candidates are not enough for a note: one typo, one unused import, or "this looks complex" without call-site proof. Fix those directly or leave a TODO.
Survey broadly
Use parallel subagents when the user asks for breadth, one domain each, evidence required. Useful domains: the message path (gateway handlers, outbox, sync feed, fanout); the pipeline (router, executor, writer, cron, watcher); the web client (hooks under apps/web/lib, components, the docs pages); runtime and host (choruz-supervisor, supervisor, connector, bridge); scripts, infra and CI. Start with the largest production files (git ls-files | xargs wc -l | sort -rn); the biggest deltas hide the duplicated lifecycle machinery.
Prove or reject each candidate
Classify consumers before writing:
- Production corpus:
crates/*/src,services/*/src,apps/*/src,apps/web/{app,components,lib,hooks},infra/,migrations/. - Non-production corpus: tests,
docs/, notes, fixtures, snapshots, comments. - Ambiguous corpus:
scripts/and the e2e harness, which may be product smoke paths.
Use git grep first: the exact symbol, the route, the event name, the table or column, the config key, the env var. Then read the call sites, the trait impls, dynamic dispatch (driver type strings, event type strings), and the SQL.
Reject or downgrade when a production caller exists and the change would be a feature decision; when an implemented note justifies the API and the new evidence does not beat it; when the removal forces unrelated churn without reducing the surface; or when the idea is correct but tiny (use a TODO with the urgency tags below).
Show full SKILL.md (285 more words)Show less
Simplify prose with the code
Comments and documentation are maintained surface area. Delete comments that restate code or explain behaviour owned elsewhere; keep required local contracts. Apply choruz-prose-standard.
Coalesce superseded Agent Notes
When a simplification makes an owning note obsolete, follow choruz-archive-agent-notes for retention judgement and mechanics. Preserve every unique rationale, alternative, consequence and reintroduction condition in the current owner; repair inbound links; delete or archive per the README's consolidation rule. Do not expand every code survey into a repository-wide note audit.
Write the Agent Note
One file per durable proposal at .agents/notes/proposed/<class>/yyyy-mm-dd-topic.md (class simplification for a removal):
# Agent Note: <action-oriented title>/Status: proposed## Problem: name the current surface, cite the files, state the consumer evidence, separating production callers from tests and docs.## Proposal: exactly what to remove, fold, or rehome, including tests, docs, migrations and selector rules.## Alternatives considered: the strongest case for keeping it, made legible.## Acceptance criteria: the observable end state and the gates that prove it.## Risks: behaviour changes, future product wants, and why the trade-off is still reasonable.
Inline TODO notes
Use FIXME (blocks a release), TODO (soon) and XXX (someday) only for small, local cleanups that are clearly useful but not durable design decisions. Name the smell with a stable tag, say why it is safe to revisit, and what action would simplify it.
Validation and PR hygiene
For note-only work run python3 scripts/verify_agent_notes.py and git diff --check. For a removal, run what choruz-pre-push-checks selects for the touched crates and specs, and git grep the removed symbols afterwards. In the PR, summarise the areas surveyed, what was intentionally excluded, the candidates added or consolidated, and the checks that passed. Use a draft PR while the survey is still expanding.
© 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-find-simplifications of inclusionAI/Choruz.
Open the folder on GitHubat commit 7509c40
Compare with similar skills
Choruz Find Simplifications 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Choruz Find Simplifications this skillinclusionAI/Choruz | 1k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
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.
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.
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.
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.
More from inclusionAI/Choruz
All 11 skills in this repoChoruz 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…
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…
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…
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…
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…
Choruz PR
inclusionAI/Choruz
Use before opening or completing a pull request in this repository — classify the change, add the tests its type requires, run exactly what CI will run, label it, merge only on a green "CI (linux)…
Related
Categories
Questions about Choruz Find Simplifications
What does Choruz Find Simplifications do?
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…. Choruz Find Simplifications is an agent skill from inclusionAI/Choruz. Use when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another branch; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-crate-exists surfaces.
When should I use Choruz Find Simplifications?
Choruz Find Simplifications fits situations like: working in this repository to find non-obvious simplification candidates; remove redundant comments; implementation-heavy documentation; write proposed Agent Notes.
How do I install Choruz Find Simplifications in Claude Code?
Run `npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a claude-code`. Or copy the skill folder (.agents/skills/choruz-find-simplifications in inclusionAI/Choruz) into .claude/skills/choruz-find-simplifications in your project. Claude Code loads it when a task matches its description.
How do I install Choruz Find Simplifications in Codex?
Run `npx skills add inclusionAI/Choruz --skill choruz-find-simplifications -a codex`. Or copy the skill folder (.agents/skills/choruz-find-simplifications in inclusionAI/Choruz) into .agents/skills/choruz-find-simplifications in your project. Codex loads it when a task matches its description.
Can I use Choruz Find Simplifications 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-find-simplifications -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-find-simplifications, .gemini/skills/choruz-find-simplifications, .github/skills/choruz-find-simplifications and .opencode/skills/choruz-find-simplifications in your project.
What does Choruz Find Simplifications need to run?
Going by SKILL.md and its folder, Choruz Find Simplifications needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3.
Does Choruz Find Simplifications 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 Find Simplifications 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 Find Simplifications use?
Choruz Find Simplifications 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 Find Simplifications use?
About 1.6k tokens (SKILL.md is roughly 6.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 Find Simplifications?
Skills that share tags, products or a category with Choruz Find Simplifications: 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 Find Simplifications?
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.