chalk

What problem does it solve?

When working on GitHub issues, code diffs fail to capture the reasoning behind changes, and unstructured comments make it hard for team members to understand the full context of work done. Issue descriptions often fall out of sync with actual progress, leading to duplicated effort and missed context when resuming work later.

Core Features & Use Cases

• Structured Session Comments: Automatically format work logs with scannable checklists and detailed explanation blocks for each task, so anyone can review what was tried, decided, and learned without sifting through chat history.
• Canonical Progress Tracking: Maintains an up-to-date ## Progress section in the issue description with a checklist of work items and status, so the issue itself always reflects the current state of work.
• Consistent Issue Voice: Enforces a standardized "chalk voice" for all GitHub-bound prose (issues, comments, PR descriptions) to ensure reasoning is clearly communicated to readers.
• Use Case: When fixing a bug reported in issue #456, use this skill to log each step of your investigation, record decisions made about root cause fixes, and update the issue's progress checklist as you complete work, so any team member can pick up the task later without additional context.

Quick Start

Use the chalk skill to track your current work session against GitHub issue #123, following the required voice and comment structure for all issue-related prose.