toki-monitor: Skill for Claude Code

Git Commit Helper Skill

Purpose

Automatically generates well-structured commit messages that follow Spec-Kit conventions and link commits to Work Packages (WP). This ensures consistent version control practices and enables automatic task history tracking in the dashboard.

When to Activate

This skill activates when users ask questions like:

• "suggest a commit message" / "커밋 메시지 추천해줘"
• "what should I commit" / "뭐라고 커밋해야 해?"
• "help me commit this" / "커밋 도와줘"
• "generate commit message" / "커밋 메시지 생성해줘"
• "commit this task" / "이 작업 커밋해줘"

Commit Message Generation Process

1. Analyze Git Status

Check current repository state:

# Get current branch
BRANCH=$(git branch --show-current)

# Check staged changes
git diff --cached --name-status

# Check unstaged changes
git diff --name-status

# Get list of modified files
git status --short

```text
**If no changes staged:**

- Inform user: "No changes staged for commit. Stage files with `git add` first."
- Optionally show unstaged changes and ask if they should be staged

### 2. Identify Current Work Package

Determine which task/WP the changes relate to:

### Method 1: From Branch Name

```bash
# Extract feature from branch (e.g., 001-user-auth)
FEATURE=$(echo $BRANCH | grep -oE '[0-9]{3}-[a-z-]+')

```text
### Method 2: From Recent Activity

```bash
# Find most recent WP file modified in tasks/doing/
find specs/*/tasks/doing/ -name "WP*.md" -type f -printf '%T+ %p\n' | sort -r | head -1

```text
### Method 3: Ask User
If unclear, ask: "Which Work Package (WP) are you working on? (e.g., WP01, WP02)"

### 3. Read Work Package Context

Once WP is identified, read the WP file to understand context:

```bash
# Example: Read WP01.md from doing lane
cat specs/{feature}/tasks/doing/WP01.md

```text
**Extract from WP file:**

- Task ID (from frontmatter `id:` or filename)
- Task title (from frontmatter `title:` or H1 heading)
- Task phase (from frontmatter `phase:`)
- Acceptance criteria (to understand what changes accomplish)