workflow-log-quickfix

Log quick mechanical changes as dated markdown files in the workflow inbox.

27|1|Updated Nov 23, 2025

Search Tags:#automation #workflow #markdown #logging #inbox #conversations #quickfix

Ready to run

npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-log-quickfix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-log-quickfix
Source: https://github.com/leeovery/agentic-workflows/tree/main/skills/workflow-log-quickfix
Command: npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-log-quickfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture quick mechanical fixes and log them as markdown entries in the workflow inbox, enabling rapid documentation for later review.

Core Features & Use Cases

Capture trivially scoped changes and record them in a standardized markdown file.
Automatically generate a dated inbox entry with a kebab-case slug for the change.
Suitable for cold starts (prompting for scope) or ongoing conversations (synthesizing from context after 1-3 exchanges).

Quick Start

Create or update a markdown file in the inbox describing the mechanical change and its rationale.

Frequently Asked Questions about workflow-log-quickfix

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

FAQPage Schema

How do I log quick fixes and mechanical changes to a markdown workflow inbox?▼

To log quick fixes, this Skill produces a dated markdown file in your workflow inbox using a kebab-case slug. It captures trivially scoped mechanical changes by drawing out the scope through conversation before finalizing the entry.

What is the best way to document small mechanical code changes for later review?▼

Documenting small mechanical changes is done by generating a standardized markdown file with a 100-300 word prose body. This creates a permanent, dated record in your inbox that enables rapid documentation for later review.

Can I use this logging workflow in a cold-start conversation or do I need existing context?▼

You can use this logging workflow in both cold-start and ongoing conversations. In cold starts, it prompts you for the scope of the mechanical change, while in ongoing conversations it synthesizes the fix from context after 1-3 exchanges.

What is the file naming convention for markdown entries generated by this workflow logging process?▼

The file naming convention for generated markdown entries follows a dated slug format: .workflows/.inbox/quickfixes/{YYYY-MM-DD}--{slug}.md. Each file contains an H1 title and a prose body documenting the change.

Does this markdown logging approach require any external dependencies or specific environment setup?▼

This markdown logging approach requires no external dependencies or specific environment setup. It operates independently to write standardized markdown files directly into your local workflow inbox directory structure.