agentleFS
Sign inStart free
Arch1eSUNArch1eSUN/Arcgentic/skills/codify-lesson/SKILL.md

codify-lesson

Skill286 starsChanged 5 months agoMITView on GitHub

Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    After round-boundary-lesson-scan reports a promotable cluster

    line 13
  2. Distinctive:

    If an amendment proposal is generated, stop for founder review before applying mandate/rule changes.

    line 35

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

codify-lesson

Scans recent audit handoffs for recurring P2/P3 patterns in structured findings tables and promotes repeated clusters into lesson cards.

When to invoke

  • After round-boundary-lesson-scan reports a promotable cluster
  • User invokes /codify-lesson
  • 3+ rounds show the same structured finding pattern

Workflow

  1. Shell out to the toolkit:

    arcgentic codify-lesson \
  --audit-dir docs/audits \
  --lessons-dir lessons \
  --amendments-dir mandates/amendments
  2. Read stdout:
    • lessons: N
    • amendments: N
    • streak_updates: N
  3. Inspect every generated lesson card before accepting it.
  4. If an amendment proposal is generated, stop for founder review before applying mandate/rule changes.

The scanner ignores reference scans, author notes, forward-debt prose, and other unstructured markdown even when those sections mention P2 or P3.

Output contract

  • New lesson card: lessons/lesson-{N}-{slug}.md
  • Formal-threshold amendment proposal: mandates/amendments/amendment-{slug}.md
  • Existing lesson streak updates when a lesson was preserved

See also

  • agents/lesson-codifier.md
  • toolkit/src/arcgentic/skills_impl/codify_lesson.py
  • toolkit/src/arcgentic/utils/pattern_detection.py

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