How this skill is triggered — by the user, by Claude, or both
Slash command
/followthrough:add-typeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new custom commitment type.
Create a new custom commitment type.
/ft add-type "name" [--display "Display Name"] [--desc "description"]
"name" - Required: Type identifier (lowercase, no spaces - will be normalized)--display "NAME" - Human-readable display name (defaults to capitalized name)--desc "TEXT" - Description of what this type is forNormalize Name: Lowercase, replace spaces with hyphens
Validate: Check type doesn't already exist
Insert: Add to commitment_types table with is_default=0
Confirm:
Created type: {name}
Display: {display_name}
Description: {description}
Use it: /ft {name} "your commitment"
/ft add-type "habit" --desc "Daily habits to build"
/ft add-type "goal" --display "Long-term Goal" --desc "Big objectives"
/ft rename-type "old" "new" - Rename a type/ft delete-type "name" --move-to "other" - Delete a typenpx claudepluginhub fredzannarbor/claude-followthrough-pluginProvides Conventional Commits patterns for writing structured, machine-readable git commit messages with types, scopes, and breaking change indicators.
Defines conventions for git branch names and commit messages using a type vocabulary. Use before creating branches or writing commits.
Composes git commit messages following Conventional Commits spec for structured history, changelogs, and semantic versioning. Use when writing commits for semantic-release, commitizen, git-cliff or indicating breaking changes.