infrastructure-work-conventions
Defines the conventions to follow when working with infrastructure and specifically terraform code.
45
46%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/infrastructure-work-conventions/SKILL.mdWhen working with terraform code and infrastructure related tasks, it's important to maintain a consistent style and structure. Here are some guidelines to help you achieve this.
Repository setup
- koenighotze/kh-gcp-seed — all IAM and service account management
- koenighotze/wheel-of-meeting — application code and infrastructure (Cloud Run, secrets, etc.) This is THIS repository
Never add IAM bindings or service account changes to wheel-of-meeting here; those belong in kh-gcp-seed.
Workflow
It is important to keep terraform valid and working. So, follow this workflow
- Always work on a fresh branch! Never on main.
- check that everything is still working
- apply your changes
- verify that everything STILL works - feel free to fix issues if you can. If something breaks, fix it and try again.
- commit your changes
- push your changes to the remote repository
BUT, if step 1. fails, DO NOT continue. Instead ask for my guidance.
How to verify infrastructure code
The easiest way is to use @scripts/check.sh. That file executes all the checks you need and will output a summary of what it found.
- Repository
- koenighotze/wheel-of-meeting
- Commit
18189d1
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.