chronicler

Name: chronicler
Availability: InStock
Author: artosetrov

Analyze recent agent activity to extract lessons and update project rules and skills.

Updated Mar 5, 2026

Search Tags:#documentation #governance #retrospectives #lessons-learned #chronicler #rules-updates

Ready to run

npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill chronicler-artosetrov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chronicler
Source: https://github.com/artosetrov/iron-fist-arena-backend/tree/main/.claude/skills/chronicler
Command: npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill chronicler-artosetrov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Scans recent work across the project, extracts patterns and lessons, and propagates improvements into rules, agent skills, and scanners to prevent repeating mistakes.

Core Features & Use Cases

Scans recent git history to identify patterns of problems and successes.
Updates DEVELOPMENT_RULES.md, CLAUDE.md, and all agent SKILL.md files with documented lessons and improved guidance.
Coordinates with scanner scripts to align checks with real-world findings and supports process improvement.

Quick Start

Run the metrics-gathering flow to generate a retrospective draft and summarize actionable rule updates.

Frequently Asked Questions about chronicler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate lessons learned from git history into development rules?▼

To automate lessons learned, this Skill scans recent git history to identify patterns and propagates those improvements directly into DEVELOPMENT_RULES.md, CLAUDE.md, and agent SKILL.md files. It generates a retrospective draft and summarizes actionable rule updates.

What is the best way to update agent skills based on recent project mistakes?▼

Updating agent skills based on project mistakes is handled by analyzing recent agent activity to extract lessons, then applying those changes across project-wide artifacts like all agent SKILL.md files. This maintains alignment and prevents repeating errors.

How do retrospectives work with scanner scripts for process improvement?▼

Retrospectives coordinate with scanner scripts by aligning checks with real-world findings from recent work. This supports process improvement by ensuring scanner scripts validate against actual patterns extracted during the retrospective analysis.

Can I propagate documentation updates across multiple project files at once?▼

You can propagate documentation updates across multiple project files at once by applying extracted lessons to project-wide artifacts such as DEVELOPMENT_RULES.md, CLAUDE.md, and all agent SKILL.md files simultaneously with documented rationale and clear guardrails.

How do I analyze recent agent activity to prevent repeating mistakes?▼

Analyzing recent agent activity to prevent repeating mistakes involves scanning recent work, gathering evidence, and performing pattern analysis. The extracted lessons are then propagated into rules and scanners to maintain project alignment.

Does generating a retrospective draft require manual evidence gathering?▼

Generating a retrospective draft does not require manual evidence gathering because the Skill runs a metrics-gathering flow that coordinates evidence collection, pattern analysis, and change propagation automatically with documented rationale.