errors-log

Extract session errors and append them to .claude/logs/tooling-issues.jsonl.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill errors-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: errors-log
Source: https://github.com/ManfronEnrico/thesis-manifold/tree/main/.claude/skills/errors-log
Command: npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill errors-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill captures errors encountered during a session (tooling failures, encoding issues, and file operation problems) and logs them to .claude/logs/tooling-issues.jsonl, providing a single source of truth for tooling problems and enabling automated documentation updates.

Core Features & Use Cases

  • Scan session history for error signals such as runtime failures, Windows/OneDrive issues, CRLF problems, and encoding errors.
  • Append structured error entries to .claude/logs/tooling-issues.jsonl and trigger a rebuild of docs/tooling-issues.md.
  • Deduplicate similar issues to prevent duplicates and streamline future debugging.

Quick Start

Run /log-errors after a session with tooling issues to log them to the JSONL file and trigger the docs tooling-issues.md rebuild.

Frequently Asked Questions about errors-log

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

FAQPage Schema
How do I log tooling errors from a session and auto-rebuild markdown docs?▼

You can log tooling errors and auto-rebuild markdown docs by invoking a command that scans session history for runtime failures, appends structured entries to a JSONL file, and triggers a markdown rebuild of the documentation.

What types of tooling issues and encoding errors can be extracted from session history?▼

Extracted tooling issues include runtime failures, Windows or OneDrive sync conflicts, CRLF line ending problems, and file encoding errors captured during the development workflow.

Can I prevent duplicate error entries when appending issues to a JSONL log file?▼

Yes, you can prevent duplicate error entries when appending to a JSONL log file because the logging process checks existing entries to deduplicate similar issues before writing structured data.

Does this logging approach work with git pre-commit workflows for comprehensive error tracking?▼

Yes, this logging approach works with git pre-commit workflows for comprehensive error tracking by automatically scanning sessions and updating JSONL logs and markdown documentation whenever tooling failures occur.

What is the best way to maintain a single source of truth for tooling failures and file operation problems?▼

The best way to maintain a single source of truth for tooling failures is to log structured error entries to a JSONL file and automatically rebuild a markdown document while deduplicating similar issues.

Why are my tooling issues not showing up in the markdown documentation after a session?▼

Tooling issues may not appear in markdown documentation if the JSONL log append fails or if the markdown rebuild trigger is not properly invoked via manual command or pre-commit integration after the session.