devops-skills CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Git workflow (MUST follow)

These rules apply to every push originating from this repo. They override default agent behavior.

1. Never push directly to main. Always create a branch (feat/<name>, fix/<name>, chore/<name>) and open a pull request.
2. No Co-Authored-By trailers. No "🤖 Generated with Claude Code" footers. No AI attribution of any kind in commit messages or PR bodies. Commits read as authored solely by the user.
3. Use the repo's git config user.name / user.email. Do not set or override identity per-commit. If unset, ask the user before configuring.
4. One logical change per branch / PR. Don't bundle unrelated edits.
5. Commit message format — imperative subject (≤72 chars), blank line, body explaining the why. Example:

   Pin Bun install to the oven-sh tap
   
   Bare `brew install bun` resolves to wrong formula on some Homebrew
   versions. Use the official tap explicitly so installs are deterministic.
   

6. Confirm before pushing. If the agent (Claude / Cursor / Codex) is about to push, list the commit summary + diff stat and ask "OK to push?" first.
7. Never --force push to a shared branch. Force-push only to your own short-lived feature branches, and only after confirming with the user.
8. PR before merge. Even for your own commits — open a PR, let CI run, then merge.

Writing style

• Never use em dash (—) or literal double-hyphen (--) in output, code comments, commit messages, docs, or skill content. Use commas, periods, or parentheses instead.
• Never use common AI filler words: delve, leverage, robust, seamless, utilize, foster, tapestry, testament, boasts, elevate, unlock, unleash, dive in, game-changer, in today's world, it's important to note. Use plain direct words instead.

Dependency / tool versions

• Before adding or pinning any dependency, package, tool version, or base image (Python, Go, Rust, Bash tooling, npm, Docker images, GitHub Actions, Terraform providers/modules, etc), check GitHub releases/tags or the official registry for the latest stable version first, then use that version. Do not guess or use a remembered/training-data version.