skills.rest
emmepra
emmepraCOMMUNITY
Explore all skills by this author →
Website𝕏@emmepraGitHub

state-logging

Maintain resumable task state and durable logs for Git-based projects.

1|1|Updated Apr 18, 2026
Search Tags:#workflow#logs#logging#verification#resume#state#CURRENT.md
One-click install
npx skills add https://github.com/emmepra/ora-et-labora --skill state-logging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: state-logging
Source: https://github.com/emmepra/ora-et-labora/tree/main/skills/state-logging
Command: npx skills add https://github.com/emmepra/ora-et-labora --skill state-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

State logging keeps work recoverable after context compaction without turning the repo into a noisy command transcript. The live state and the historical log are separate artifacts with different jobs.

Core Features & Use Cases

  • initialize branch-local task state
  • keep CURRENT.md short, current, and overwrite-in-place
  • keep the task log append-only and delta-only
  • record verification verdicts and evidence paths without copying large artifacts
  • provide a reliable compaction recovery path

Quick Start

Initialize a new resumable task workspace and start tracking state with CURRENT.md and the task log.

Frequently Asked Questions about state-logging

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

FAQPage Schema
How do I keep task state resumable after context compaction in Git?▼

Keep task state resumable by splitting live state into a short CURRENT.md file and an append-only task log. This separation provides a deterministic recovery path after context compaction without cluttering the repository.

What's the best way to track verification verdicts and evidence in a durable log?▼

Track verification verdicts by appending delta-only entries to the task log. Record evidence paths rather than copying large artifacts, keeping the historical record compact while maintaining full traceability for Git-based recovery.

How does CURRENT.md work for managing live task state in multi-step work?▼

CURRENT.md works as a short, overwrite-in-place file capturing live branch-local task state. It stays current by being overwritten, contrasting with the append-only task log that records historical deltas for resumable recovery.

When do I need durable state logging for multi-step Git branches and PRs?▼

You need durable state logging when multi-step work involving issues, branches, worktrees, PRs, and releases exceeds a single chat session. It initializes branch-local task state to ensure work remains recoverable across context compaction.

Can I use state logging to recover work across different Git worktrees?▼

Yes, state logging initializes branch-local task state designed for multi-step work with Git worktrees. It provides a deterministic recovery workflow aligning with defined state surfaces to resume work seamlessly after interruptions.

Related Skills

Explore More Software Engineering Skills→
All-The-VibesAll-The-Vibes
50

git-clean-gone-branches

Identify and delete local git branches with deleted remote-tracking branches.

Official
Intermediate
hamzashakoor119hamzashakoor119

session-state-manager

Save and reload conversation state in timestamped session logs.

Community
Advanced
erclxerclx
2

claude-orchestrate

Coordinate multi-agent development workflows by managing task queues and roadmap sequencing.

Community
Advanced
m43num43nu

end

Save MARVIN session transcripts, update state, and optionally commit to git.

Community
Advanced