agentleFS
thunderockthunderock/thunderkit/skills/tk-fast/SKILL.md

tk-fast

Skill2 starsChanged 29 days agoMITView on GitHub

Use when a change is trivial and local (a typo, a rename, a one-line fix, a config value): edit inline in the current session with no model selection, plan, subagents or review, run the targeted test and make one atomic commit; escalate to tk-quick when it stops being trivial.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All of these must hold before starting:

    line 21
  2. Very specific:

    no path listed in frozen_paths in .thunderkit/config.json is touched.

    line 24
  3. Very specific:

    Stop and hand the task to tk-quick (or tk-router for larger work) when any of these becomes true during the edit:

    line 29
  4. Distinctive:

    Read the files you will change.

    line 56
  5. Distinctive:

    Run the targeted test or check.

    line 58
  6. Distinctive:

    Only that separate controller has the scoped checkpoint exception.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

tk-fast: trivial edits, inline

tk-fast is the smallest path through thunderkit. It is for a change you can describe in one sentence and verify with one command: a typo, a rename inside one module, a one-line fix, a config value. It does not choose a model, write a plan, spawn subagents or ask for a review. The current session does the edit.

When to use

All of these must hold before starting:

  • the change touches at most 3 files;
  • no path listed in frozen_paths in .thunderkit/config.json is touched;
  • one targeted test or check command can show the change works.

Escalation

Stop and hand the task to tk-quick (or tk-router for larger work) when any of these becomes true during the edit:

  • a fourth file needs changing;
  • a frozen path would change;
  • the targeted test still fails after one fix attempt.

Report the escalation with the files touched so far; do not commit partial work.

Delegation

On Claude Code, Codex, Copilot and other GSD hosts the only native target is GSD gsd-fast (thunderkit-delegates: gsd:gsd-fast). It needs no GSD project under .planning/ and binds no model class. Check the route first:

python3 scripts/tk-resolve.py --skill tk-fast --operation edit --config .thunderkit/config.json --capabilities <snapshot> --lock .thunderkit/peers.lock.json --json

delegate means hand the task to gsd-fast and keep this skill's scope and escalation rules. fallback means use the inline procedure below. blocked means stop and report the reason. OpenCode and Hermes have no fast target, so the resolver returns fallback / unsupported_host there. A missing lock returns peer_unlocked: print npx thunderkit peers --host <host> and use the fallback. The resolver result is a routing decision, not evidence that an edit happened.

Fallback

  1. Read the files you will change.
  2. Make the edit.
  3. Run the targeted test or check.
  4. Make one atomic Conventional Commit containing only this change.

The edit stage permits no push, PR, tag or publish. Never skip the test to make the path faster. Save current context and unfinished changes before escalation or pause, then have the approved checkpoint controller run checkpoint_cli.py capture under the shared preservation rule. Only that separate controller has the scoped checkpoint exception; native workers remain delivery-disabled. Preservation does not require a plan, model selection or a partial commit.

Output contract

change: <one sentence>
files: <paths>
check: <command> -> <exit code>
commit: <sha> <subject> | none (escalated)
route: delegate gsd-fast | inline (<reason_code>) | escalated -> tk-quick

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.