القائمة
Use this skill when adding, updating, validating, or reporting on the governed Fakoli operating-model principles ledger.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used AFTER code review and verification pass, when the user wants to "ship this", "ship the task", "open and merge the PR", "push, PR, wait for CI, and merge", or otherwise run the mechanical tail of a one-PR-per-task loop. It pushes the current branch, opens a PR, waits for CI to reach a terminal state, merges (squash + delete branch), syncs the base branch, and optionally runs a post-merge command (e.g. `anvil apply`). It makes NO review decisions — the human or agent gates that first.
Mine past coding-agent sessions (Claude Code, Codex, OpenClaw, Cursor CLI) into local-model eval suites executable via anvil-serving. Retro-first — consumes session-retro output dirs and cross-session findings themes, curates candidates into deterministic check-based evals sized for local models, emits anvil-serving-compatible eval-data suites, and runs them against any OpenAI-compatible endpoint. Use when the user asks to "create evals from my sessions", "build local-model evals", "turn this retro into evals", "which work classes can my local model handle", or wants evidence for anvil-serving routing decisions. Reads only local session logs; writes only to the eval-data root the user chooses.
Generate spec-INDEPENDENT breakage probes for a change — attack it along fail-closed, malformed-input, resource-exhaustion, and state-drift axes, not by re-reading its own tests. Use before opening a PR, as anvil execute's verify-left stage, when the user asks to "recall-mode verify", "red-team this change", "what breaks this", "find failure modes", or wants an independent breakage pass that doesn't reuse the implementer's assumptions. Reports findings; does not fix.
Scan source for Windows/cross-platform CLI hazards before shipping — non-ASCII in printed strings (the cp1252 console crash), hardcoded python3, heredoc backslash mangling, Node .cmd/.bat spawns, set -e in hooks. Use when the user asks to "check for encoding issues", "scan for Windows portability", "cli hygiene", is about to ship a CLI/script change, or wants the deterministic form of the ship-loop Windows discipline. Advisory (never blocks); wire it as a gate-router gate.
Route changed file paths to the verify commands this repo requires before shipping — docs changed means docs strict build, shell changed means bash -n, CLI changed means the encoding smoke test. Use before committing/opening a PR, when the user asks "what checks do I need to run", "run the gates", "gate check", or after substantive edits in a repo with a .claude/gate-router.local.md rules file. Deterministic local gates instead of session memory; also helps AUTHOR the rules file for a new repo.
Save or update this project's cross-session handoff note — the resume point for the next session, shared across checkouts of the same git remote and across linked worktrees. Use when the user types /handoff (optionally with a one-line summary), says "save a handoff", "note where we are for next time", "write a handoff before I clear context", or is wrapping up a session.
| name | style-ops |
| description | Use this skill when adding, updating, validating, or reporting on the governed Fakoli operating-model principles ledger. |
Skill for operating the Fakoli Style principles ledger. The canonical source of truth is data/principles.json; docs/fakoli-style.md is a generated projection. Edit the data, not the doc, then regenerate.
Lifecycle rule: a principle cannot reach proven unless its proof field resolves to a real test file on disk. The validator enforces this and exits non-zero on any violation.
Append a new principle entry to data/principles.json. New entries default to aspirational and require an open_work field describing what work would raise the status. After editing, regenerate and validate.
# 1. Edit data/principles.json: add an entry with status "aspirational" and open_work
# 2. Regenerate the doc
uv run --script scripts/generate.py
# 3. Validate the ledger
uv run --script scripts/validate.py
Run both commands from plugins/fakoli-style/.
Advance a principle's lifecycle status by editing its entry in data/principles.json. Rules by target status:
asserted: add proof (repo-relative file path) and a non-empty embodied_in array.proven: same as asserted, but proof must point to a test file (test_*.py, *_test.py, or a file under a tests/ directory). The validator rejects a proven entry whose proof is not a test file.After editing, regenerate and validate:
uv run --script scripts/generate.py
uv run --script scripts/validate.py
Run both commands from plugins/fakoli-style/.
Run the full ledger validator. Checks schema validity, duplicate IDs, proof-path existence, embodiment-path existence, the proven-requires-test rule, and staleness of the generated doc.
uv run --script scripts/validate.py
Exits 0 with OK: ledger and generated doc are valid and in sync. Exits 1 with FAIL: <reason> on any violation.
Read the status of all principles. Two options:
Generated doc (formatted table):
# Open docs/fakoli-style.md and read the "At a glance" table
cat docs/fakoli-style.md
Quick jq summary (counts by status):
jq '[.principles[].status] | group_by(.) | map({(.[0]): length}) | add' data/principles.json
Run from plugins/fakoli-style/.
Full documentation: README.md
Ledger: data/principles.json
Generated doc (do not hand-edit): docs/fakoli-style.md