Maintain and update the persistent project chronicle (docs/chronicle.md). Trigger when: - The human requests a history summary or chronicle update. - Starting work on a new codebase and needing context on its evolution. - Prompt contains keywords: /chronicle, chronicle, project history, git log summary, history summary.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
A structured approach to maintaining a high-level, conceptual project chronicle (docs/chronicle.md). This chronicle serves as a persistent decision record, mapping the evolution of the codebase's architecture, workflows, and conventions to optimize agent context and human understanding.
Standard git logs are either too detailed or too fragmented to provide deep architectural context. The Chronicle Workflow maintains an incremental, high-level chronicle file in the repository. Because it uses a commit cutoff marker in its frontmatter, it can be updated cheaply and incrementally over time, serving as a durable project history journal.
To update or initialize the chronicle, follow these steps:
Run the helper script in prepare mode:
python3 skills/chronicle/scripts/update_chronicle.py --prepare
If the chronicle is already up to date, the script will output:
Chronicle is already up to date with HEAD. and you may exit.
Otherwise, it will output a batch of up to 50 commits (from oldest to newest) along with changed files. Note the TARGET_END_SHA printed at the end of the output — you pass it back to the write step so the recorded range is bound to exactly the commits you summarized (immune to HEAD moving in between).
Using your LLM reasoning, analyze the batch output. Group the commits into conceptual themes rather than listing them raw. Focus on why changes were made, what design decisions were reached, and major milestones.
Organize the summary into the following categories where relevant:
Run the helper script in write mode, passing the TARGET_END_SHA from Step 1 and your structured Markdown summary:
python3 skills/chronicle/scripts/update_chronicle.py --write --end-sha <TARGET_END_SHA> --summary "<Markdown formatted summary>"
If the write command output indicates remaining pending commits (e.g., Remaining pending commits: N), repeat from Step 1 until the prepare command reports that it is fully up to date.
The chronicle summaries should be written in clean, concise Markdown. Avoid listing individual commit SHAs in the summary text (the headers already track the ranges). Example format:
- **Architectural Shift**: Distilled global ruleset to align with axiom/persona conventions.
- **Workflow & Rulesets**: Formalized planning workflows by adding `SKETCH` and `PLAN` protocols.
- **Quality & Infrastructure**: Ignore cache files and standardize tooling in the root configuration.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
SOP for auditing AI-generated code. Trigger when: - Reviewing, refactoring, or cleaning up AI-generated code to prevent regressions or hallucinated APIs. - Prompt contains: /ai-audit, code audit, AI cleanup, common flaws.
The English summary is being prepared. Showing the original description.
Protocol for auditing API surface coherence and type safety. Trigger when: - Evaluating API designs, interface type safety, or design elegance. - Prompt contains: /api-audit, API surface, API coherence, type safety.
The English summary is being prepared. Showing the original description.
Normative sufficiency conditions for Initial Boundary Conditions (IBCs) and the SOP for the cheap-tier boundary refinement loop (/boundary). Trigger when: - Crafting, auditing, or refining a prompt/IBC destined for an expensive (architect-class) model or an autonomous worker dispatch. - Evaluating whether a task frame is sufficient to bound an agent walk. - Prompt contains: /boundary, IBC, initial boundary condition, boundary contract, sufficiency conditions, worker prompt, prompt refinement.
The English summary is being prepared. Showing the original description.
SOP for the architect-tier campaign workflow (/campaign): exhaustive survey, mitigation planning, tiered orchestration, and reconciliation. Trigger when: - Running a multi-workstream initiative where an expensive architect-tier council surveys, plans, emits worker prompts, and judges landed work. - Conducting production-readiness assessments that fan out into autonomous mitigation dispatches across model tiers. - Prompt contains: /campaign, campaign workflow, survey, orchestrate, reconcile, premise freshness, tier routing, worker IBC, scratch.
The English summary is being prepared. Showing the original description.
Rules, conventions, and constraints for formatting git commit messages and committing at logical boundaries. Trigger when: - Drafting, revising, or validating git commit messages. - Pausing at commit boundaries under the CORE or CONTINUE workflows. - Evaluating whether a changeset should be split into multiple commits. - Prompt contains keywords: commit message, git commit, conventional commits, commit hygiene, commit guidelines, logical boundary, spaghetti diff, atomic commit, commit boundary.
The English summary is being prepared. Showing the original description.
Foundational ethics, authority hierarchy, and structural principles for the Predicate agent. Always-on law (composable system-prompt core): Truth>Harmony, Evidence>Authority, Halt>Assumption, Outcomes>Process — four ordered principles that govern every walk. Reference (by-moment): conflict resolution, ethics adjudication, novel situations, precedence walkthrough, entropy diagnostics, principled resistance. Trigger (reference depth): resolving rule conflicts, ethics calls, novel situations. Prompt contains: constitution, principles, precedence, truth over harmony, outcomes over process, evidence over authority, principled resistance.
The English summary is being prepared. Showing the original description.