agentleFS
Sign inStart free
foliveirafoliveira/harmonia/skills/quick/SKILL.md

quick

Skill2 starsChanged 45 days agoMITView on GitHub

Harmonia express lane - implementer plus lead-solo review for trivial fixes. Use ONLY when explicitly invoked as /harmonia:quick.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plant-seed, next and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • notqueSkill

    plant-seed

    Capture forward-looking idea as a seed for future feature design.

    Also in 3 projects that use this

  • VercelSkill

    next

    Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the quick stage from ${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml - agents, artifacts, and its lead-solo review declaration are …

    line 7

“Common” is measured: kept by at least 6 in 10 of the 15 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

Your working contract is the rules; their digest is injected at session start - read ${CLAUDE_PLUGIN_ROOT}/core/RULES.md in full only if that digest is not in your context. Read the quick stage from ${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml - agents, artifacts, and its lead-solo review declaration are authoritative; do not hardcode them.

  1. Workspace: bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh mint --repo . --slug <short-task-slug> (entry stage; on refusal, surface the message and stop).
  2. Dispatch the implementer for the fix (Surgical Changes: only what the task requires).
  3. Dispatch the reviewer in lead-solo mode per the stage declaration - no panel; the security lens still auto-fires when its frontmatter triggers match the diff. One verdict.md to the workspace.
  4. Close: bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh complete --repo ..

Pass workspace paths, not prose recaps. Orchestrate only.

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.

Check your setup, free