Agent skill

Patchies Workflow

by heypoom in heypoom/patchies

A skill your agent uses when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.

AGPL-3.0Auto-check passed

Install Patchies Workflow

skills CLI
$ npx skills add heypoom/patchies --skill patchies-workflow -a claude-code

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

GitHub CLI
$ gh skill install heypoom/patchies patchies-workflow --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/heypoom/patchies.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/patchies-workflow .claude/skills/patchies-workflow && 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
patchies-workflow
GitHub stars
209
Token cost
~712 tokens
SKILL.md length
308 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.

  • Working in Patchies on tests
  • SKILL.md covers Specs, Testing, Verification and Formatting, plus 2 more sections
  • Calls git
  • Verification scope

What it does

Patchies Workflow is an agent skill from heypoom/patchies. Use when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Write small programs with tools & libraries you know and patch 'em together. Make interactive widgets, visuals, sounds, and play with computation on the web. The licence is AGPL-3.0.

When your agent uses it

  • Working in Patchies on tests
  • Verification scope
  • Especially before changing product behavior
  • The user explicitly asks to commit

Example prompts

  • “/patchies-workflow”

What it can do on your machine

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

    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

Patchies Workflow loads about 712 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 308 words of instructions outside code blocks.

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

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 heypoom/patchies at commit dd38c74, republished under its AGPL-3.0 licence (© heypoom). 308 words, ~712 tokens.

Download SKILL.mdSave it as .claude/skills/patchies-workflow/SKILL.md (or your agent's skills folder).
name
patchies-workflow
description
Use when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.

Patchies Workflow

Specs

  • Before non-trivial feature, architecture, behavior, or product design changes, update the relevant file in docs/design-docs/specs/.
  • Specs must be numbered in both filename and title, for example 50-foo-bar.md and # 50. Foo Bar.
  • Do not create or update a spec for trivial localized changes such as spacing, typo fixes, or aligning a single node with an existing pattern.

Testing

  • Test observable behavior through public APIs, rendered UI, store state, emitted events, tool results, or user-visible outcomes.
  • Do not test source text, imports, prompts, declarations, or implementation shape unless that exact wording or shape is user-visible product behavior.
  • Do not add guardrail tests that only lock code structure.
  • If behavior is embedded in a prompt, component, or declaration object, prefer extracting real decision logic and testing its inputs and outputs.
  • For declaration-only changes such as preset code strings, static metadata, prompts, or config tables, prefer careful review plus targeted typecheck or lint over brittle tests.

Verification

  • Run the narrowest useful command first. Broaden only when the touched surface warrants it.
  • Use git diff --check for patch hygiene after edits.
  • Report noisy, blocked, or partial checks honestly.

Formatting

  • In multiline code, use blank lines to separate setup, configuration, side effects, and return values.
  • Format chained calls one method per line when that makes the setup easier to scan.

Commits

Never commit or push unless the user explicitly asks.

When asked to commit, use short imperative messages:

text
scope: description
type(scope): description
type(scope)!: description
type: description

Common types: fix, feat, refactor, docs, spec, add, chore.

Use the object name as the scope when changes are object-specific. Use the module name when changes are module-specific.

Examples:

text
transport: make transport panel beat indicator zero-indexed
feat(clock)!: use absolute time by default in parameter automation messages
fix(transport): reset lastPlayState on unsubscribe
refactor(orca): extract settings component into OrcaSettings
docs: shorten time signature docs
add beat object

Rules:

  • Lowercase the first word after the colon.
  • Do not add a period.
  • Keep under about 72 characters.
  • Use imperative mood.

Reflections

After significant refactors, create docs/reflections/YYYY-MM-DD-topic.md with:

  • Objective
  • Key Challenges & Solutions
  • What Could Be Better
  • Action Items

Consult existing reflections before similar work.

© heypoom, AGPL-3.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/patchies-workflow of heypoom/patchies.

Open the folder on GitHubat commit dd38c74

Compare with similar skills

Patchies Workflow 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.

Patchies Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Patchies Workflow this skillheypoom/patchies209—~712Automated safety check: PassAGPL-3.0
Spec Writergarrytan/gstack136k—~14kAutomated safety check: NotesMIT
Reflectalirezarezvani/claude-skills28k1 repos~2.4kAutomated safety check: PassMIT
Specgarden-co/classic-jazz2.5k—~1.3kAutomated safety check: PassMIT
Spec Driven Workflowalirezarezvani/claude-skills28k—~3.9kAutomated safety check: PassMIT
Reflection Coachpaperclipai/paperclip98k—~3kAutomated safety check: PassMIT

Similar skills

  • Spec Writer

    garrytan/gstack

    Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.

    136k GitHub stars~14k tokensUpdated today
    DevelopmentAuto-check: notes
  • Reflect

    alirezarezvani/claude-skills

    Mid-conversation reflection skill that pauses execution and zooms out from detail-mode to honestly reassess direction, assumptions, and bias.

    28k GitHub starsUsed in 1 repo~2.4k tokens
    Agent WorkflowsAuto-check passed
  • Spec

    garden-co/classic-jazz

    Implement features using Spec Driven Development (SDD) workflow.

    2.5k GitHub stars~1.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Spec Driven Workflow

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first…

    28k GitHub stars~3.9k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Reflection Coach

    paperclipai/paperclip

    Reflect on another agent's recent execution record and propose the smallest durable instruction, skill, or tool-description change.

    98k GitHub stars~3k tokensUpdated today
    Sales & SupportAuto-check passed
  • Sparc Spec

    ruvnet/ruflo

    Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

    74k GitHub stars~1.1k tokensUpdated today
    Product & Project ManagementAuto-check: notes

More from heypoom/patchies

All 8 skills in this repo
  • Patchies Audio

    heypoom/patchies

    A skill your agent uses when adding, migrating, or changing Patchies Audio V2 nodes, native DSP worklet nodes, audio object docs, audio packs, or AudioService integration.

    209 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Patchies Frontend

    heypoom/patchies

    A skill your agent uses when editing Patchies Svelte components, UI state, styling, buttons, persistence, or frontend implementation patterns.

    209 GitHub stars~992 tokensUpdated today
    Auto-check passed
  • Patchies Objects

    heypoom/patchies

    A skill your agent uses when adding, editing, or migrating Patchies nodes, objects, handles, object modules, schemas, object docs, AI prompts, file drag/drop support, or node data settings.

    209 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Patchies Assembly Module

    heypoom/patchies

    A skill your agent uses when changing Patchies assembly VM code, VASM Rust sources, wasm-pack output, machine WASM assets, asm object behavior, or modules/vasm build/link steps.

    209 GitHub stars~341 tokensUpdated today
    Auto-check passed
  • Docs Style

    heypoom/patchies

    Patchies documentation style guide. An agent skill from heypoom/patchies.

    209 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Patchies Rendering

    heypoom/patchies

    A skill your agent uses when changing Patchies rendering pipeline, render graph, image generation preview capture, GLSystem, render workers, FBO rendering, output sizing, render-node types, or video…

    209 GitHub stars~656 tokensUpdated today
    Auto-check passed

Questions about Patchies Workflow

What does Patchies Workflow do?

A skill your agent uses when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit. Patchies Workflow is an agent skill from heypoom/patchies. Use when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.

When should I use Patchies Workflow?

Patchies Workflow fits situations like: working in Patchies on tests; verification scope; especially before changing product behavior; the user explicitly asks to commit.

How do I install Patchies Workflow in Claude Code?

Run `npx skills add heypoom/patchies --skill patchies-workflow -a claude-code`. Or copy the skill folder (.agents/skills/patchies-workflow in heypoom/patchies) into .claude/skills/patchies-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Patchies Workflow in Codex?

Run `npx skills add heypoom/patchies --skill patchies-workflow -a codex`. Or copy the skill folder (.agents/skills/patchies-workflow in heypoom/patchies) into .agents/skills/patchies-workflow in your project. Codex loads it when a task matches its description.

Can I use Patchies Workflow 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 heypoom/patchies --skill patchies-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/patchies-workflow, .gemini/skills/patchies-workflow, .github/skills/patchies-workflow and .opencode/skills/patchies-workflow in your project.

What does Patchies Workflow need to run?

Going by SKILL.md and its folder, Patchies Workflow needs the command-line tools its instructions call (git).

Does Patchies Workflow 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 Patchies Workflow 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 Patchies Workflow use?

Patchies Workflow is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Patchies Workflow use?

About 712 tokens (SKILL.md is roughly 2.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 Patchies Workflow?

Skills that share tags, products or a category with Patchies Workflow: Spec Writer (garrytan/gstack, 136k stars), Reflect (alirezarezvani/claude-skills, 28k stars), Spec (garden-co/classic-jazz, 2.5k stars) and Spec Driven Workflow (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Patchies Workflow?

heypoom (a GitHub user) maintains it in heypoom/patchies, which has 209 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.

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