
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
CLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.
Maven CLI invocation patterns. Use whenever running `mvn` commands in Java/Maven projects. Covers when `-am` is required, why `-o` (offline) mode hides bugs in multi-worktree setups, and how to verify compile/test cleanly without trusting stale `~/.m2` artifacts.
MUST be loaded before creating, editing, or reviewing any SKILL.md, agent markdown, or command markdown file. Contains formatting rules that prevent common mistakes like numbered steps, which cause git churn. Also use when the user asks about instruction formatting best practices, header structure, or how to avoid unnecessary diffs.
Enforce Maven POM dependency ordering rules. This skill should be used when editing pom.xml files.
Running precommit checks and build validation. ALWAYS use after ANY code changes.
Work with markdown-based task lists in .llm/todo.md files. Use when managing tasks, working with todo lists, extracting incomplete tasks, marking tasks complete, or implementing tasks from a task list.
Coordination guidelines for leading a team of task-executing agents
This skill should be used when the user asks to "fix formatter-off", "fix code generation formatting", "fix auto-formatted string concatenation", "add formatter off", or when writing, reviewing, or generating Java code generators that build source code via string concatenation. Also applies proactively when creating new code generation methods or modifying existing ones — always use @formatter:off guards and the one-output-line-per-source-line convention.
Conversation style guidelines. Use when responding to the user.
Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
Guidelines for working with LLM context stored in the .llm/ directory.
OpenRewrite recipe test maintenance. Use when fixing test failures, import ordering issues, type validation problems, IDE warnings, or writing comprehensive recipe tests.
OpenRewrite recipe authoring patterns and API best practices. Use when writing or editing OpenRewrite recipe Java source code (visitors, matchers, type checks, templates, metadata, YAML config, list transformations, at-scale validation).
Coordinates other skills and agents. ALWAYS use this skill on startup.
Workflow guidelines for team members executing tasks
Temporal database patterns for system-time versioned tables. Use when working with tables that have system_from/system_to columns, temporal queries, non-destructive updates, merge/sync logic, rollback, or schema migrations involving temporal data.
Code quality guidelines. ALWAYS use skill for ANY code changes.
Offline Claude Code documentation fallback. Use when the user asks about Claude Code features, capabilities, or configuration and the built-in claude-code-guide subagent fails due to network issues or proxy blocking.
Guidelines for comments in code. Use when adding, editing, or removing comments.
This skill should be used when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs.
Efficient data loading patterns using system_from/system_to for cache validation. Use when implementing incremental sync, conditional fetches, polling for changes, ETags, high watermarks, or avoiding redundant data transfer in systems with temporal tables.