agentleFS
Sign inStart free
dimitar-radenkovdimitar-radenkov/Pointframe/.agents/skills/kb-done/SKILL.md

kb-done

Skill15 starsChanged 25 days agoMITView on GitHub

Close a Pointframe work session - bring the knowledge base up to date or confirm it is unchanged, run the KB check, run the done gate, write the status checkpoint (coordinator), and report. Use when the user types /kb-done, and at the end of every task or session before the final message.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Do these in order. Skip a step only when it cannot apply.

    line 10
  2. Very specific:

    Check: Run pwsh scripts/kb.ps1 check, then pwsh scripts/kb.ps1 check -NoFix, and fix every ERROR until it prints 0 errors.

    line 13
  3. Very specific:

    Done gate: When C# changed, run dotnet format Pointframe/Pointframe.csproj.

    line 14
  4. Very specific:

    Status checkpoint (coordinator only): Follow "Status and handoff" in docs/knowledge-base/workflow.md: pwsh scripts/status.ps1 -Set for each …

    line 15

≈ “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

/kb-done: finish every session here

/kb-done [-Role coordinator|executor|reviewer] closes the work. The role defaults to the one this session's /kb-init used, else executor. It does not commit, push, or merge; executors never do, and the coordinator does those through the workflow's own steps.

Do these in order. Skip a step only when it cannot apply; with no changes at all, say so and stop after step 2.

  1. Knowledge base. Run pwsh scripts/kb.ps1 changed -Base <merge-base of HEAD and origin/master>; the uncommitted changes count too. For each section or feature it lists, apply the /kb-write rules: update it, or record reviewed unchanged: <reason> for the final message. A renamed or moved file always needs an update. A reusable trap you diagnosed in this session goes to lessons.md and is linked from its owning section.
  2. Check. Run pwsh scripts/kb.ps1 check, then pwsh scripts/kb.ps1 check -NoFix, and fix every ERROR until it prints 0 errors.
  3. Done gate. When C# changed, run dotnet format Pointframe/Pointframe.csproj. Then run pwsh scripts/verify.ps1 until it prints VERIFY PASSED, iterating on the failure details. After several honest attempts, or if passing would need a weaker test, stop and report what fails and why.
  4. Status checkpoint (coordinator only). Follow "Status and handoff" in docs/knowledge-base/workflow.md: pwsh scripts/status.ps1 -Set for each active task, then pwsh scripts/status.ps1 -Publish. Never hand-edit the generated regions.
  5. Final message, short. KB (updated sections, reviewed unchanged with reasons, or nothing), check result, verify result, and what is left open.

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