DevOps engineering conventions for team. CI/CD, infra-as-code, observability. Project conventions in .claude/conventions/devops.md override these defaults.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
DevOps conventions, team default.
Project override: if `{repo}/.claude/conventions/devops.md` exists, overrides any rule here. See guides/conventions-override.md.
## Defaults
CI/CD:
- GitHub Actions for most repos. Workflows in `.github/workflows/`.
- Reusable workflows when steps repeat across repos.
- Secrets via GitHub Secrets, never inline.
- Pin actions to commit SHA, not branch.
Containers:
- Multi-stage Dockerfile. Slim base images (alpine, distroless).
- Non-root user in production stage.
- `.dockerignore` mirrors `.gitignore` essentials plus build artifacts.
Infra-as-code:
- Terraform for infra. State in remote backend (S3, etc).
- Modules in `terraform/modules/`. Stacks in `terraform/stacks/`.
- Variables via `terraform.tfvars`, never hardcoded.
Observability:
- Grafana dashboards JSON in repo when applicable.
- Alerts as code (Prometheus rules, Datadog monitors).
- Log structure: JSON, with `trace_id`, `service`, `level`, `msg`.
Secrets:
- Never commit secrets. Use secret manager.
- Pre-commit hook to scan for accidental secrets.
## Before writing code
Read at least 3 similar workflows or terraform modules in repo. Confirm:
…
The line at the top of this page pins the label git:20260519.492683a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1766 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
pierry/harness-kit · 4 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vselcw3bkry25k2d
GET https://markdownregistry.com/api/v1/resolve?ref=pierry/harness-kit/devops
GET https://markdownregistry.com/api/v1/blob/698a0b5d52b6aa4664a4d39928451a142d55b2d32aaf12ca9e293555f0fae8eb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
pierry/harness-kit · .claude/agents/product-manager/skills/prd/SKILL.md · Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.
pierry/harness-kit · .claude/agents/product-manager/skills/prp/SKILL.md · Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/backend/SKILL.md · Backend engineering conventions for team. Java/Kotlin servers. Project conventions in .claude/conventions/backend.md…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/mobile/SKILL.md · Mobile engineering conventions for team. iOS and Android. Project conventions in .claude/conventions/mobile.md override…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/web/SKILL.md · Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override…
pierry/harness-kit · .claude/agents/system-architect/skills/design/SKILL.md · Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook…
pierry/harness-kit · .claude/agents/system-architect/skills/review/SKILL.md · Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and…
pierry/harness-kit · .claude/agents/system-architect/skills/search-engine/SKILL.md · Design a web-scale search engine (crawler, processing, indexing, query serving). Topic playbook from the System Design…
vanducng/skills · skills/devops/SKILL.md · Deployment and infrastructure operations. Use when writing or debugging a Dockerfile, docker build/run, docker compose…
