agentleFS
helmut-hoffer-von-ankershoffenhelmut-hoffer-von-ankershoffen/heinzel/.claude/skills/scaffold-plugin/SKILL.md

scaffold-plugin

Skill2 starsChanged 16 days agoMITView on GitHub

Create a new Heinzelmännchen plugin repository from the copier template, or update an existing plugin to the latest template. Use when asked to create, scaffold or bootstrap a Heinzelmännchen plugin, or to bring a plugin up to date with Heinzelmännchen's standards.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the author guide, including the separate public/private repository paths.

    line 10

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scaffold a plugin

New plugin

Read the author guide, including the separate public/private repository paths.

  1. Outside an existing Git repository, run hz system plugin new heinzel-<name> --defaults --data plugin_name=<name>. The minimal preset is one operation and behavior test; use --preset contributions only when settings, views, Today or notifications are useful.
  2. cd heinzel-<name> && make setup && make check-fast. Setup initializes Git and creates the owning lock and environment. Follow generated AGENTS.md; CLAUDE.md uses the same instructions.
  3. Edit the owning operation and behavior test. Use public heinzel / heinzel.kernel contracts. A model or service is optional. Add ordinary dependencies to the owning pyproject, then make lock.
  4. make fix, make check-fast, make check, make build, make acceptance; make preview uses isolated state. These commands use installed artifacts and never run the core suite. CORE=<wheel> selects a candidate SDK.
  5. Host in the requested public or private repository, and add topic heinzel-plugin for catalog discovery. Private installation uses the installing person's gh login. make release previews; after review and merge, make publish selects private GitHub or public PyPI publication. Public PyPI needs the owning trusted publisher; private sources must stay off PyPI. Independent tags are <distribution>/v<version>.

Inside an existing repository, use hz system plugin new plugins/heinzel-<name> --defaults --layout collection --data plugin_name=<name>, or the host's optional new shortcut with NAME=<name>. Keep all feature files in the new directory and run the same owning Make commands from there. Root NAME=<owner> shortcuts are optional. Never create an embedded repository or copy parent workflows.

Update an existing plugin

From a clean owning repository, run uvx copier update --defaults --vcs-ref vX.Y.Z, resolve conflicts, refresh its lock and run owning checks/build/acceptance. Commit as chore(template): update to heinzel vX.Y.Z. Retained governed repositories also have the make update-template wrapper. Do not replace owning source or tests with another plugin.

New templates live in starter/; template/ retains the governed layout. make template-test checks both against installed core/toolkit artifacts, including a new authored operation in each small preset and layout.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.