dev-log-convert

Converts raw daily work notes into structured past-tense English work logs with normalized ticket IDs and totalled time.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/envoydev/claude-stack --skill dev-log-convert-envoydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-log-convert
Source: https://github.com/envoydev/claude-stack/tree/main/stack/skills/dev-log-convert
Command: npx skills add https://github.com/envoydev/claude-stack --skill dev-log-convert-envoydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning messy end-of-day notes (often in Ukrainian, English, or mixed) into a clean, consistent work log is repetitive and error-prone - ticket IDs need normalizing, times need summing, and multi-project days need grouping. This Skill automates that conversion into a strict, copy-ready format. ## Core Features & Use Cases - Structured log generation: Converts raw notes into a dated, past-tense English work log with ticket IDs uppercased, times normalized (h/m, decimal hours, Ukrainian units), and a verified total. - Multi-prefix and multi-day grouping: Groups tasks by project or ticket prefix, orders groups by time spent, and splits multi-day input into per-day sections with resolved dates. - Verified time totals: Drafted lines are checked with a bundled Node.js script (scripts/total-time.js) so the printed Total time always matches the sum of the entries. - Use Case: Paste a day's mixed Ukrainian/English notes like 'ABC-1319 - 2г досліджував проблему...' and receive a formatted log block ready to submit, with edge cases (relative dates, day off, tickets spanning days) handled per references/edge-cases.md. ## Quick Start Type 'dev-log' followed by your raw work notes for the day and ask for the structured work log.

Frequently Asked Questions about dev-log-convert

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

FAQPage Schema
How do I convert raw work notes into a daily work log?▼

Invoke the skill with the exact keyword 'dev-log' and paste your raw notes for one or more days. It outputs a fenced log with numbered tasks, normalized ticket IDs, per-task times, and a verified Total time line.

How are ticket IDs and time values normalized in the work log?▼

Ticket IDs matching [A-Z][A-Z0-9]*-digits are uppercased, obvious prefix typos corrected, and unticketed work labeled Other. Times accept Ukrainian units (г, год, хв) and decimal hours, and are normalized to h/m format like 1h 30m.

Can the work log handle Ukrainian or mixed-language input?▼

Yes, Ukrainian or mixed Ukrainian/English notes are translated to English by default. If you explicitly ask to keep Ukrainian output, the log is produced in Ukrainian instead; Russian is never used.

Does the skill support multi-day or multi-project work logs?▼

Yes, multi-day input produces a separate dated section per day, and days with multiple ticket prefixes are grouped by project name or prefix. Groups are ordered by total time, with numbering restarting inside each group.

What happens when the input only gives a total time estimate?▼

The skill stops and asks before splitting a total or estimate across days or tasks - it never invents the split. A task with no time at all is marked '(time not specified)' and counts as zero in the total.

When should I not use the dev-log-convert skill?▼

Do not use it for general note-taking, meeting minutes, commit messages, or status updates - it fires only on the exact 'dev-log' keyword and produces one specific work-log format.