claude-code-config

Set up or bootstrap a project with the claude-code-config tooling — setup-project.sh, install-tooling.sh, the layered hooks setup, and the new-repo runbook. Use when installing this config into a repo, running the setup scripts, vendoring the make-check tooling, or bootstrapping a new project.

Create a new "Later" backlog item (Learn / Research / Do / Read) from a configurable template.

Install or update the shared MkDocs Material style layer (Ink & Indigo on warm paper) in the current project.

Prepare technical analysis for backlog refinement meetings.

Capture a quick status update and append it to today's daily log.

Prepare end-of-week review notes summarizing the full week's work activity across all sources (Git, GitHub, Jira).

Prepare a standup document summarizing recent work activity across Git, GitHub, and Jira.

Use when working with Git repositories, branches, commits, pull requests, release workflows, or files under .git — including complex operations like interactive rebase, merge-conflict resolution, cherry-picking, bisecting, or recovering lost commits via reflog.

Use when writing or reviewing authentication, authorization, middleware, routes, input validation, secrets handling, JWT, CSRF, CORS, or security-sensitive code paths. For a full audit of pending changes, use the bundled /security-review command instead.

Create a pull request with a well-crafted description. Use when the user finished work on a branch and wants to open a PR, or asks to create a pull request.

Create an Architecture Decision Record (Nygard format) documenting a technical decision. Use when the user is deciding between multiple technical approaches, evaluating trade-offs for a framework/library/database choice, planning a schema migration or multi-component refactor, or explicitly asks for an ADR.

Analyze staged changes and write a conventional commit message. Use when the user has staged git changes and asks to commit, or wants help writing a commit message.

Create a hotfix branch with a minimal fix, targeted tests, and PR. Use when the user describes an urgent production bug, says "hotfix", or asks for a quick fix to ship to main.

Guide a TDD (Test-Driven Development) workflow with disciplined Red-Green-Refactor cycles for the given feature or change. Use when the user is starting a new feature or behavior change and asks for TDD.

Use when designing or reviewing REST APIs, including views, routes, controllers, endpoints, serializers, schemas, status codes, pagination, and error response formats.

Use when editing Django models, views, serializers, admin, managers, signals, migrations, querysets, or database access patterns.

Use when editing Dockerfiles, Docker Compose files, container build contexts, .dockerignore files, or container security and caching patterns.

Use when editing Terraform, Kubernetes manifests, Helm charts, infrastructure modules, or deployment configuration.

Use when investigating incidents, production failures, recurring bugs, regressions, flaky tests, logs, stack traces, or system behavior that needs root-cause analysis.

Use when writing or reviewing tests, fixtures, factories, mocks, test coverage, or files named test_*, *_test, *.test.*, or *.spec.*.