log-iteration

Log codebook development iterations as YAML trails with version, commit, and decisions.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill log-iteration
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: log-iteration
Source: https://github.com/estebandegetau/Fiscal-shocks/tree/main/.claude/skills/log-iteration
Command: npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill log-iteration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Log a codebook development iteration with auto-gathered metrics, user interpretation, and a reusable YAML trail stored under prompts/iterations/.

Core Features & Use Cases

  • Auto-capture codebook version, git commit, date, stage, and changes
  • Record user interpretation and final decision for each iteration
  • Append structured entries to a per-codebook iteration log for traceability and auditing

Quick Start

Invoke /log-iteration after running a pipeline stage to record an auditable iteration in prompts/iterations/ for the current codebook.

Frequently Asked Questions about log-iteration

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

FAQPage Schema
How do I log codebook iterations for reproducibility?โ–ผ

You log codebook iterations by recording an auditable YAML-based trail that captures version, commit, stage, changes, results, interpretation, and decisions to support reproducibility and governance.

What is an iteration log used for in codebook development?โ–ผ

An iteration log provides traceability and auditing for codebook development by auto-capturing metrics, user interpretations, and final decisions into a structured YAML trail stored under prompts/iterations/.

How do I track codebook version and git commit history for auditing?โ–ผ

You track codebook version and git commit history by auto-capturing this data into a structured YAML iteration log, recording stage, changes, and results to support traceability and auditing.

Can I record user interpretation and decisions in a codebook iteration log?โ–ผ

Yes, you can record user interpretation and final decisions for each iteration. The log appends structured entries to a per-codebook iteration file for traceability and governance.

When do I need a YAML traceability log for prompts?โ–ผ

You need a YAML traceability log for prompts when you want to audit codebook iterations with auto-gathered metrics. It captures version, date, stage, and changes to support reproducibility.

Do I need dependencies to audit codebook iterations with auto-metrics?โ–ผ

No dependencies are required to audit codebook iterations. The skill operates independently to log version, commit, stage, changes, and results in a YAML trail for reproducibility.