Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add Arch1eSUN/Arcgentic --skill codify-lesson --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Codify Lesson?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/arch1esun-codify-lesson)More formats (shields.io, HTML) on the badges page.
---
name: codify-lesson
description: Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.
---
# 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:
```bash
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`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.