textcharts

This skill should be used when the user asks to "plan a blog post", "research for blog", "draft a blog post", "critique a draft", "deformulize a post", "commit blog changes", "editorial review", "voice check", "style check", "audit blog", "content audit", "audit series", or "audit drafts".

This skill should be used when the user asks to "commit code", "review code", "fix lint/type error", "improve performance", "compare code", "shrink code", "generate spec from code", "investigate code", or "create handoff prompt".

This skill should be used when the user asks to "create documentation", "build docs", "review docs", "compare documents", "compress docs", "adversarial review docs", or "commit docs".

Unified identify-verify-stage-commit logic reused by other skills.

Semantic comparison workflow for validating equivalence between artifacts.

Pre-edit investigation workflow for understanding code and behavior before changes.

Validation-driven compression workflow that requires semantic comparison before approval.

Post-edit verification workflow for lint, typecheck, tests, and spot checks.

This skill should be used when the user asks to "sync skills", "set up skill-sync", "check skill status", "validate skills", "preview skill changes", "diagnose skills", "pin a skill", "unpin a skill", "prune skills", or "promote skill changes".

This skill should be used when the user asks to "run tests", "create tests", "fix failing test", "add test coverage", "fix slow tests", or "commit test changes".

Consolidate accumulated Claude Code permission grants — move trusted commands from settings.local.json into wildcard rules in settings.json, clean up garbage entries, commit project-level settings.

This skill should be used when the user asks to "create a TODO", "manage TODOs", "show TODO items", "prioritize TODOs", "implement a TODO", "review TODOs", "complete a TODO", "cleanup TODOs", "create TODOs from spec", or "initialize TODO system".