Claude Skills by BrennonTWilliams

Analyze user message history to suggest FSM loop configurations automatically. Uses ll-messages output to identify repeated workflows and generate ready-to-use loop YAML. Also supports --from-commands mode to suggest loops from the available command/skill catalog without requiring message history, and --from-sequences mode to suggest loops from ll-logs sequences n-gram output. Trigger keywords: "suggest loops", "loop from history", "automate workflow", "create loop from messages", "analyze m...

Manage releases - create git tags, generate changelogs, and manage GitHub releases. Integrates with Issue Management to include completed issues in release notes. Trigger keywords: "manage release", "create release", "new release", "tag release", "publish release", "make release", "bump version"

Find and fix issue filenames with missing or duplicate IDs across types (e.g., BUG-007 and FEAT-007)

Open a pull request for the current branch. Trigger keywords: "open pr", "create pull request", "submit pr", "create pr", "open pull request", "submit for review", "make a pr"

Analyze issues and prepend priority levels (P0-P5) to filenames

Analyze and validate an issue file for accuracy, utility, and completeness, then auto-correct to make implementation-ready or close if invalid

Refine issue files with codebase-driven research to fill knowledge gaps needed for implementation

Resume from a previous session's continuation prompt

AI-guided sprint health check that analyzes a sprint's current state and suggests improvements - removing stale issues, adding related backlog issues, and identifying dependency or contention problems. Pairs with `ll-sprint edit` (mechanics) the way `/ll:create-sprint` pairs with `ll-sprint create` (intelligence). Trigger keywords: "review sprint", "sprint health", "sprint review", "check sprint", "sprint suggestions", "optimize sprint", "sprint health check", "is my sprint still good"

Run test suites with common patterns

Scan codebase to identify bugs, enhancements, and features, then create issue files

Scan codebase for product-focused issues based on goals document

Sync local issues with GitHub Issues (push/pull/status). Trigger keywords: "sync issues", "push to github", "pull from github", "github sync", "sync with github", "export issues", "import issues from github"

Toggle automatic prompt optimization settings

Evaluate active issues for utility vs complexity trade-offs and recommend which to implement, update, or close. Use this skill to sense-check your backlog before implementation, prune low-value issues, or during sprint planning to focus on high-value work. Trigger keywords: "tradeoff review", "review issues", "utility review", "prune backlog", "issue tradeoff", "sense check issues", "evaluate issues", "backlog review", "worth implementing", "low value issues"

Verify issue files for accuracy, relevance, and completeness by testing claims against actual code

Use when asked for a second opinion from a different, stronger model on a specific decision, question, or stalled judgment call.

Use when asked about project health, velocity, bug trends, or whether we're making progress.

Use when asked to audit Claude Code config, validate plugin settings, or diagnose plugin issues.

Use when asked to audit documentation accuracy, coverage, or find documentation gaps.

Use when asked to detect conflicting requirements or incompatible decisions across open issues.

Use when asked to assess loop effectiveness, audit goal achievement, or detect phantom success.

Use when asked to capture or create an issue from conversation or natural language.

Use when asked to clean up stuck loops, kill dead loop processes, or troubleshoot loop state.

Use when asked to manually compact a session's memory, trigger session summarization, or reduce a long session's context footprint.

Use when asked for a pre-implementation confidence check or whether an issue is ready to implement.

Use when asked to configure little-loops, change settings, or update ll-config.json.

Use when asked to generate an FSM eval harness YAML from one or more issue IDs, or DSL eval tasks from a loop/issue file with --dsl.

Use when asked to create an automation loop or automate a recurring task with an FSM.

Use when asked to analyze loop execution history, investigate loop failures, or find loop issues.

Use when asked to select the winning implementation option for an issue with decision_needed.

Use when asked to extract reusable loop patterns or YAML fragments from successful execution history.

Use when exploring an external API/library and recording proof to the Learning Test Registry.

Use when asked to format an issue or fix its template structure.

Use when asked for an adversarial go/no-go review or whether an issue is worth implementing.

Use when asked to improve or rewrite CLAUDE.md or increase LLM instruction adherence.

Use when asked to initialize little-loops, set up ll for a project, or bootstrap config.

Use when asked to evaluate issue size, decompose large issues, or audit backlog complexity.

Use when asked about the issue lifecycle, command order for issues, or how to manage issues.

Assign orphaned issues to existing EPICs, or cluster them into new-EPIC proposals, via `ll-issues link-epics`.

Validate active issues against key documents for relevance and alignment

Analyze user message history to identify patterns, workflows, and automation opportunities

Analyze codebase architecture for patterns, organization, and improvements

Use when asked to capture or create an issue from conversation or natural language.

Run code quality checks (lint, format, types, build)

Clean orphaned git worktrees from interrupted ll-parallel/ll-loop runs

Create git commits with user approval and no assistant attribution

Use when asked to manually compact a session's memory, trigger session summarization, or reduce a long session's context footprint.

Create a sprint definition with a curated list of issues

Generate comprehensive PR descriptions following repository templates