idea-to-code

Capture mistake or improvement opportunity with 5 whys analysis

Stage all changes, review the uncommitted changes, generate a descriptive commit message, and commit changes.

Ignore unstaged changes, review the staged changes, generate a descriptive commit message, and commit changes.

Run ./gradlew precommitCheck before committing changes

Walk me through the design decisions in the design document one by one. This includes:

Consult the design pattern catalog before implementing or refactoring code.

When stuck on a problem, formulate a well-structured question and copy it to the clipboard for pasting into ChatGPT. Claude should use this skill when debugging efforts stall or when an outside perspective would help.

Provides a pre-commit checklist and commit message formatting standards for this project. Claude should use this skill when creating git commits to ensure messages follow project conventions, including proper co-authorship attribution and concise formatting.

Guidelines for watching CI builds and diagnosing failures. Claude should use this skill when watching a CI build or investigating why a CI build failed.

Provides Dockerfile best practices for this project. Claude should use this skill when creating or modifying Dockerfiles to ensure optimal layer caching by ordering instructions from most stable to least stable.

Guidelines for file operations like moving, renaming, and reorganizing files. Claude should use this skill when reorganizing code structure to prefer efficient shell commands over write/delete patterns.

Find all production code locations where a class, function, or method is defined and used. Use when the user asks where something is defined, instantiated, invoked, or called in production code.

Guidelines for resolving git merge and rebase conflicts efficiently. Claude should use this skill when resolving merge conflicts or rebase conflicts to prefer bulk git strategies over manual conflict marker editing.

Provides a GitHub Actions CI workflow template for Gradle/Java projects. Claude should use this skill when creating or updating CI workflows to ensure current action versions and best practices are followed.

Guidelines for incremental development practices. Claude should use this skill when writing multiple similar files (tests, classes, configurations) to ensure each piece is verified before moving to the next.

Guidelines for structural operations on plan files (renumbering). Claude should use this skill when the user asks to renumber or fix numbering in a plan file, or after inserting, deleting, or reordering threads/tasks.

Guidelines for working with plan files. Claude should use this skill when the user provides a plan file (e.g., *-plan.md) to ensure task completion is tracked in the plan file itself, not just internally.

a workflow for practicing Test-Driven Development (TDD)

When running test scripts or long-running commands that produce verbose output, redirect output to a log file under logs/ to avoid truncation in the Bash tool. Claude should use this skill when running test scripts, end-to-end tests, or any command likely to produce large output.

a definition of tests and testing in a Java project using Gradle and JUnit 5

how to structure and write tests (shell) scripts involving infrastructure

Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.

Summarize the current discussion into an idea file. Use when the user asks to capture an idea, write an idea file, or after a discussion identifies a refactoring or feature worth pursuing.

7 hooks across 5 events