Claude Skills by cowwoc

Find and read multiple files in one operation (50-70% faster for exploration)

Gather results from completed subagent including commits, metrics, and state updates

Compare two documents semantically with relationship preservation to identify content and structural differences

Split oversized task into smaller tasks with proper dependency management

Guide for formatting Claude-facing documentation with proper line wrapping and YAML multi-line syntax

Access raw conversation history from Claude Code session storage for analysis

Reference for accessing session ID via ${CLAUDE_SESSION_ID} automatic substitution

MANDATORY: Use instead of `git commit --amend` - verifies HEAD and push status first

Guide for writing clear, descriptive commit messages

Merge task branch to base branch with linear history (works from task worktree)

MANDATORY: Use instead of `git rebase` - provides automatic backup and conflict recovery

MANDATORY: Use instead of `git filter-branch` - safer git-filter-repo with recovery

MANDATORY: Use instead of `git rebase -i` for squashing - unified commit messages

Find and read multiple files in one operation (50-70% faster for exploration)

Analyze mistakes with conversation length as potential cause (CAT-specific)

Merge subagent branch into task branch with conflict resolution and cleanup

Check status of running subagents including token usage and context limits

Orchestrate multiple independent subagents concurrently with coordinated collection

Create and register hook scripts with proper error handling and settings

**Purpose**: Release a new version of a Claude Code plugin by merging to main, tagging, and preparing the next version branch. **CRITICAL**: Always use this skill for releases. Update CHANGELOG.md before running `git tag`. The skill ensures changelog, version files, and tags stay synchronized. **When to Use**: - When user says "release", "publish", "tag a new version", or similar - After completing work on a plugin version branch - When ready to publish a new plugin version

MANDATORY: Use BEFORE showing ANY diff to user - transforms git diff into 4-column table with box characters (╭╮╰╯│). Required for approval gates, code reviews, change summaries.

Run scheduled retrospective analysis, derive action items, and track effectiveness

Safely remove code patterns from multiple files with validation and rollback (project)

MANDATORY: Use instead of rm -rf or rm -r to prevent shell session breakage

Compress documentation while preserving execution equivalence (validation-driven approach)

Use BEFORE creating or updating any skill OR command - decomposes goal into forward steps via backward reasoning

Launch subagent with task context in isolated worktree with token tracking

Multi-perspective quality review gate with architect, security, quality, tester, and performance stakeholders

> **See also:** [tdd.md](../../concepts/tdd.md) for TDD philosophy and when to use TDD vs standard implementation. Use Test-Driven Development for features that benefit from upfront behavior specification. **Invoke for:** - Adding features with testable inputs/outputs - Fixing bugs (test captures the bug first) - Implementing validation, parsing, or transformation logic - Building state machines or workflows **Skip TDD for:** - UI layout and styling - Configuration changes - Glue code with no...

Generate detailed token usage report with threshold analysis and recommendations

MANDATORY: Run before git push --force, rebase, or reset to verify safety

Create file and commit atomically (60-75% faster than step-by-step)

Render boxes and tables with proper emoji-aware alignment using box-drawing characters