Agent skill

Besimple Tiny Broccoli

by besimple-oss in besimple-oss/broccoli

Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASESHA..HEAD).

MITAuto-check passedDevelopment

Install Besimple Tiny Broccoli

skills CLI
$ npx skills add besimple-oss/broccoli --skill besimple-tiny-broccoli -a claude-code

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

GitHub CLI
$ gh skill install besimple-oss/broccoli besimple-tiny-broccoli --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/besimple-oss/broccoli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/prompt-templates/skills/besimple-tiny-broccoli .claude/skills/besimple-tiny-broccoli && 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
besimple-tiny-broccoli
GitHub stars
285
Token cost
~1.2k tokens
SKILL.md length
541 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASESHA..HEAD).

  • Works in 6 steps: Record BASE_SHA (required) → Choose the repo check command(s) once… → Implement the requested change (required) → …
  • Development work in your project
  • SKILL.md covers Not for, Preconditions (hard stop if…, Required subskills and Workflow, plus 1 more section
  • Calls git, npm and python3

What it does

Besimple Tiny Broccoli is an agent skill from besimple-oss/broccoli. Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASESHA..HEAD).

Its SKILL.md is about 1.2k 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. It works with npm, Git and Python. The repository describes itself as: Broccoli turns Linear tickets into shipped PRs — powered by Claude and Codex, running on your own Google Cloud or Blaxel containers. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/besimple-tiny-broccoli”

Requirements

  • Python 3

Workflow steps

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

  1. Record BASE_SHA (required)
  2. Choose the repo check command(s) once (required)
  3. Implement the requested change (required)
  4. Run repo checks and fix only what you broke (required)
  5. Commit once checks are green (required)
  6. Run dedup against BASE_SHA (required)

What it can do on your machine

Read from SKILL.md and the folder at commit 6cad3b9. 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:

    • git
    • npm
    • python3
    • poetry

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

  • Network

    No URLs in SKILL.md. Its commands use git and npm, 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

Besimple Tiny Broccoli loads about 1.2k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 541 words of instructions outside code blocks.

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

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 besimple-oss/broccoli at commit 6cad3b9, republished under its MIT licence (© besimple-oss). 541 words, ~1,242 tokens.

Download SKILL.mdSave it as .claude/skills/besimple-tiny-broccoli/SKILL.md (or your agent's skills folder).
name
besimple-tiny-broccoli
description
Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASE_SHA..HEAD).

Tiny Broccoli: Implement → Check → Commit → Dedup

Use this when the user request is already clear and you can safely implement directly (no plan docs), but you still want:

  1. repo checks to be green, and
  2. a dedupe pass over the resulting diff.

Not for

  • Big/ambiguous work that needs research, design decisions, or a multi-phase plan.
  • “Refactor the whole repo” style requests.

Preconditions (hard stop if missing)

  • Confirm you are in the intended repo: git rev-parse --show-toplevel
  • Start from a clean working tree: git status --porcelain is empty
  • Ensure git can create commits (user.name / user.email configured)
  • Ensure required CLIs exist (dedup requires distinct vendors): codex, claude

Required subskills

  • dedup

Workflow

0) Record BASE_SHA (required)

Capture the base ref before any changes (used later for dedup):

bash
BASE_SHA="$(git rev-parse HEAD)"
1) Choose the repo check command(s) once (required)

Do a one-time tooling detection + configuration so the per-step “build/lint” commands match the target repo.

Detect languages and entrypoints

  • Node/TS: look for package.json in repo root and common subprojects (for example functions/package.json).
  • Python: look for pyproject.toml, uv.lock, poetry.lock, requirements.txt. Pick build/lint/typecheck commands (prefer repo-native scripts)
  • Prefer existing package scripts when present (e.g. npm run build, npm run lint, npm test).
  • Prefer the repo’s configured Python toolchain:
    • If uv is clearly in use: use uv-based commands.
    • If Poetry is clearly in use: use poetry run ....
    • If neither: use the repo’s documented commands (README/CONTRIBUTING) if available.
  • If multiple options exist or it’s unclear, ask the user once for the canonical build/lint/typecheck commands, then reuse them for every step. Write down a “Tooling config” block and reuse it for every step
  • Example format (adapt to the repo):
    • Root (Node): build=..., lint=...
    • functions/ (Node): build=..., lint=...
    • Root (Python): build=..., typecheck=..., lint/format=...
  • From now on, only run the commands from this block after each step (instead of hard-coded defaults). If the repo has no build/lint tooling
  • Explicitly record “No build/lint configured” and skip build/lint steps (do not invent tooling). Call this out in the final summary.
Show full SKILL.md (217 more words)Show less
2) Implement the requested change (required)
  • Make the smallest correct change that satisfies the request.
  • Prefer reusing existing patterns/utilities over creating new ones.
  • Keep the change set small and reviewable.
3) Run repo checks and fix only what you broke (required)
  • Run the commands from your Tooling config.
  • If checks fail due to changes you introduced, fix and re-run until green.
  • If checks fail for clearly pre-existing/unrelated reasons, stop and report:
    • the exact command(s) you ran, and
    • the first actionable error output.
4) Commit once checks are green (required)
  • git add -A
  • Make a single atomic commit for the user-requested change:
    • git commit -m "<imperative summary>" (example: Fix flaky upload retry).
  • Do not create empty/no-op commits (--allow-empty is prohibited).
5) Run dedup against BASE_SHA (required)

Ensure the working tree is clean, then run the dedupe loop:

bash
if [ -n "$(git status --porcelain)" ]; then
  echo "Working tree is not clean; commit or stash before running dedup." >&2
  exit 1
fi
bash
resolve_skill_dir() {
  local name="$1"
  local repo_root=""
  repo_root="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

  local candidates=(
    "$repo_root/.agents/skills/$name"
    "$repo_root/.claude/skills/$name"
    "$HOME/.agents/skills/$name"
    "$HOME/.codex/skills/$name"
    "$HOME/.claude/skills/$name"
  )

  for d in "${candidates[@]}"; do
    if [[ -d "$d" ]]; then
      echo "$d"
      return 0
    fi
  done

  echo "Error: skill '$name' not found in repo-scoped or user-scoped skill dirs." >&2
  return 1
}

DEDUP_SKILL_DIR="$(resolve_skill_dir dedup)"
python3 "$DEDUP_SKILL_DIR/scripts/run_dedup_loop.py" "${BASE_SHA}"

If dedup creates additional commits, re-run the Tooling config checks once at the end and fix only issues introduced by dedupe changes. Do not interrupt/restart the dedup loop if it looks quiet; the loop script owns timeouts and retries.

Guardrails

  • Keep changes tightly scoped to the user request + required dedupe.
  • Avoid drive-by refactors, renames, formatting-only churn, or dependency upgrades unless required.
  • End state must be: checks green (or explicitly “no checks configured”), clean working tree, and at least one meaningful commit.

© besimple-oss, MIT. 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 prompt-templates/skills/besimple-tiny-broccoli of besimple-oss/broccoli.

Open the folder on GitHubat commit 6cad3b9

Compare with similar skills

Besimple Tiny Broccoli 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.

Besimple Tiny Broccoli compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Besimple Tiny Broccoli this skillbesimple-oss/broccoli285—~1.2kAutomated safety check: PassMIT
Manor PR Prepmanor-os/manor-ai162—~585Automated safety check: PassCustom licence
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
MCP AuthoringOtoDock/oto-dock190—~1.3kAutomated safety check: NotesCustom licence
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Manor PR Prep

    manor-os/manor-ai

    A skill your agent uses when preparing a Manor branch or change set for pull request, final review, commit, merge readiness, PR body, verification summary, or checking that tests/docs/self-hosted…

    162 GitHub stars~585 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes
  • MCP Authoring

    OtoDock/oto-dock

    Author an MCP package for OtoDock: the manifest.json fields and their rules, the package layout, what the installer refuses or drops, credentials and instances, skills bundled with an MCP, and the…

    190 GitHub stars~1.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check: notes
  • 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
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    46k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

More from besimple-oss/broccoli

All 10 skills in this repo
  • Broccoli Oss GCP Deploy

    besimple-oss/broccoli

    Deploy this repository to a new Google Cloud project using the repo's existing Cloud Run, Cloud Run Jobs, Cloud SQL, Secret Manager, and Artifact Registry scripts.

    285 GitHub stars~4.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Plan Critique Loop

    besimple-oss/broccoli

    Critique and revise an existing plan doc up to 3 iterations, using accept/reject triage and stopping early when no important feedback remains.

    285 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Plan Sketch

    besimple-oss/broccoli

    Do bounded research (official docs first) and produce a high-level implementation sketch in sketch/<generated-name.md.

    285 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Plan Write

    besimple-oss/broccoli

    Write a detailed, self-contained implementation plan to a new Markdown file under plan/.

    285 GitHub stars~721 tokensUpdated 5 mo ago
    Auto-check passed
  • Claude Simplify Wrapper

    besimple-oss/broccoli

    Run Claude's built-in /simplify skill on BASESHA..HEAD, validate checks, and commit.

    285 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Code Review Loop

    besimple-oss/broccoli

    Iterative review+fix loop for BASESHA..HEAD: generate findings, apply accepted fixes, run checks, commit, and re-review up to 3 iterations or until clean.

    285 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Besimple Tiny Broccoli

What does Besimple Tiny Broccoli do?

Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASESHA..HEAD). Besimple Tiny Broccoli is an agent skill from besimple-oss/broccoli.HEAD).

When should I use Besimple Tiny Broccoli?

Besimple Tiny Broccoli fits situations like: development work in your project.

How do I install Besimple Tiny Broccoli in Claude Code?

Run `npx skills add besimple-oss/broccoli --skill besimple-tiny-broccoli -a claude-code`. Or copy the skill folder (prompt-templates/skills/besimple-tiny-broccoli in besimple-oss/broccoli) into .claude/skills/besimple-tiny-broccoli in your project. Claude Code loads it when a task matches its description.

How do I install Besimple Tiny Broccoli in Codex?

Run `npx skills add besimple-oss/broccoli --skill besimple-tiny-broccoli -a codex`. Or copy the skill folder (prompt-templates/skills/besimple-tiny-broccoli in besimple-oss/broccoli) into .agents/skills/besimple-tiny-broccoli in your project. Codex loads it when a task matches its description.

Can I use Besimple Tiny Broccoli 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 besimple-oss/broccoli --skill besimple-tiny-broccoli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/besimple-tiny-broccoli, .gemini/skills/besimple-tiny-broccoli, .github/skills/besimple-tiny-broccoli and .opencode/skills/besimple-tiny-broccoli in your project.

What does Besimple Tiny Broccoli need to run?

Going by SKILL.md and its folder, Besimple Tiny Broccoli needs the command-line tools its instructions call (git, npm, python3 and poetry). Our summary lists: Python 3.

Does Besimple Tiny Broccoli access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Besimple Tiny Broccoli 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 Besimple Tiny Broccoli use?

Besimple Tiny Broccoli is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Besimple Tiny Broccoli use?

About 1.2k tokens (SKILL.md is roughly 5k 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 Besimple Tiny Broccoli?

Skills that share tags, products or a category with Besimple Tiny Broccoli: Manor PR Prep (manor-os/manor-ai, 162 stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), MCP Authoring (OtoDock/oto-dock, 190 stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Besimple Tiny Broccoli?

besimple-oss (a GitHub organization) maintains it in besimple-oss/broccoli, which has 285 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on April 26, 2026.

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