claude

easy-cheese

Cheese your code πŸ§€ β€” high-quality results as easy as cheese. A portable, harness-agnostic Agent Skills toolkit.

19 on GitHubMITupdated 3 days ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin easy-cheese in paulnsorensen/easy-cheese. Commands read from the repo's manifest β€” 3 days ago.

What it installs

Skills (18)

  • python-authoring

    Write, edit, refactor, or review Python in easy-cheese with concise stdlib-first code, Python 3.12, wedge .pyz packaging, and repository test and validation conventions. Use for Python changes under src/, scripts/, .github/scripts/, or tests/, especially when the user asks for Pythonic, succinct, de

  • skill-authoring

    Codify the discipline-section guidance, the CSO description rule, and the size-budget checklist that easy-cheese skills follow when authoring or revising a skill. Use when writing a new skill or SKILL.md, adding a discipline section, or reviewing an existing skill against easy-cheese's authoring con

  • affinage

    Triage a GitHub PR's review comments, CI failures, and merge conflicts through the /age lens. Use when the user says "address the PR feedback", "fix the review comments on PR 123", "fix CI on my PR", "resolve this PR's merge conflicts", or "/affinage". Do not use for a diff without a PR. Use /age in

  • age

    Review a diff, PR, branch, or path across thirteen dimensions. Emit a severity-grouped findings report. Use when the user wants a code review. Trigger on "review this", "/age", "is this safe to merge", or "find bugs". Also trigger on "spot security issues", "check for slop", "review my PR", or "what

  • briesearch

    Researches cited evidence from documentation, current web sources, repositories, local code, and Git hosting. Use when the user asks to research, compare, investigate, verify facts, find guidance, assess maintenance, or gather evidence before implementation. Trigger on "research X", "compare A vs B"

  • cheese

    Route an idea, path, pull request, issue, failure, question, or bare `/cheese` to the correct workflow skill. Use this skill for `/cheese`, routing requests, help requests, or opening messages without a named workflow skill.

  • cook

    Implement an approved spec or focused task through stale-safe source edits. Use this skill when the user says "implement this", "cook this spec", or "fix this bug". Use it for `/cook .cheese/specs/<slug>.md`. Also use it when the user says "go" with clear acceptance criteria. Run it alone for an una

  • culture

    Models problems and trade-offs without writing code or specifications. Use when a workflow needs silent reasoning, or the user asks for "/culture", "no writes", "rubber-duck this", or "these bugs feel connected". Not for specs (/mold), code (/cook), or bug diagnosis and fixes (/pasteurize).

  • cure

    Apply selected fixes from an /age report, findings list, or CI failure. Run the project gates and hand a clean result to /plate. Use when the user wants selected findings resolved. Do not use for review, test authoring, or direct publication.

  • easy-cheese-setup

    Register the durable `cheese-durable` Hallouminate corpus. Repair the durable corpus when its configuration changes. Register the repository tenant. Repair the repository tenant when its configuration changes. Use this skill when the user requests durable corpus setup or repair. Use it when the user

  • hard-cheese

    Checks whether an author can explain a code change before review. Use when the user requests `/hard-cheese`, `/cheese --hard`, or an understanding check. Use it before a pull request or through the `--hard` pipeline flag. Do not use it for reviews, test hardening, or fixes.

  • melt

    Resolve content conflicts during Git merge, rebase, cherry-pick, pull, or branch integration. Use for CONFLICT, unmerged paths, or Git's "needs merge" diagnostic for an unmerged path. Trigger on fix merge conflicts, resolve rebase conflicts, cherry-pick conflict, and similar requests. Do not use for

  • mold

    Turn a high-leverage design decision into a validated spec through grounded dialogue. Use it when a leverage trigger fires (auth, irreversible effects, concurrency, contracts, destructive ops, a new slice, a cross-slice dependency, an invariant gap) or when the user asks for a spec or design. Typica

  • pasteurize

    Diagnose and fix a hard bug. Build a reliable reproduction, name the cause, add a regression test, and apply the minimum fix. Use when the user reports a bug, a failure, a flaky test, a performance regression, an error, or a wrong result whose cause is unknown. Use when the user pastes a symptom, a

  • plate

    Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all s

  • press

    Run the tests-only adversarial pass that `/cook` dispatches after a behavior change; also callable as a manual re-run. Use this skill when the user says "press the changes", "harden this", "re-run press", or "/press". Do not edit production code.

  • ultracook

    Retired β€” /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.

  • wheypoint

    Mark the current conversation as a durable handoff so a new agent can resume the work. Use when the user wants to preserve state for a later or parallel session. Triggers include "hand this off", "write a handoff", "drop a wheypoint", "checkpoint this", "compact the conversation", and "/wheypoint".

View source on GitHub cheeselord.dev

Maintain easy-cheese?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted