Skip to content

DEVLOG.md

Latest commit

 

History

History
53 lines (39 loc) · 2.76 KB

DEVLOG.md

File metadata and controls

53 lines (39 loc) · 2.76 KB

claude-todo-skill — Development Log

A living record of architectural decisions, milestones, key insights, and strategic direction. Auto-maintained via claude-devlog-skill. Entries are reverse-chronological.

[2026-03-26] Added lint check requirement to SKILL.md

Category: feature Tags: lint, code-quality, skill-behavior, cross-tool Risk Level: low Breaking Change: no

Summary

Added a "Lint Check" subsection to the Project Context section, requiring the skill to verify the target project has a linter configured on first use per session.

Detail

  • New subsection placed after "Project Context (First Use Per Session)", before the TODOS.md format section
  • Same stack-appropriate linter list as all other code-katz tools: Ruff, ESLint/Biome, SwiftLint, golangci-lint, clippy, pre-commit
  • Part of a cross-tool effort to standardize lint checks across all code-katz tools

Decisions Made

  • Consistent with devlog and roadmap skills — all three project-context-aware skills now check for linting in the same place during their setup flow

[2026-03-20] v1.0 — Initial release

Category: milestone Tags: release, v1, initial Risk Level: low Breaking Change: no

Summary

First release of the claude-todo-skill. A lightweight, per-project todo tracker that lives alongside devlog and roadmap skills.

Detail

Built to solve a simple problem: ideas and small tasks surface mid-conversation and disappear. This skill gives them a home — a flat TODOS.md checklist with three interactions: add, list, and review.

Design decisions:

  • No categories, priorities, due dates, or tags — kept deliberately minimal per user intent ("just a list of ideas to track")
  • No git commit on write — TODOS.md is a scratchpad, not a changelog; user can commit manually if desired
  • No approval gate for /todo add — single-item writes are low-stakes, confirm immediately
  • Show-before-write for /todos review — multi-item changes shown first, then written once
  • Completed items stay inline as - [x] — never moved to a separate section
  • Progress notes use indented sub-bullets with date prefix

Decisions Made

  • Flat list vs. sections: Chose flat. Adding sections (Open / Done) adds ceremony for no benefit at this scope.
  • Commit on write: Chose not to. Devlog and roadmap commit because they're architectural artifacts. Todos are transient scratchpad content.
  • One skill file vs. two: Chose one. Both todo and todos commands are handled in a single SKILL.md, triggered by matching invocation.
  • Delete option in review: Not included in v1. "Done" is sufficient for clearing items; if the user wants to remove an item, they can ask explicitly.