Giorgio Crivellari miticojo

Coding rules — always apply.

1. Spec-driven. Build exactly what's asked. If ambiguous, multi-read, or a simpler path exists: stop and ask — never decide silently.

2. YAGNI / KISS. Minimum code that solves it. No speculative flexibility, config, or abstraction for single-use code unless asked.

3. Surgical. Change only what the request needs; every line traces to it. Match existing style; don't touch unrelated code. Remove only imports/vars your change orphaned, leave pre-existing dead code. Keep changes small; refactors separate from features.

4. TDD. Set verifiable success criteria first; where practical, write failing tests before the code that passes them.

Step by step procedure

If you need to setup a cross project trigger from Cloud Source Repository (aka CSR) to Cloud Build (aka CB), one way could be this one:

Setup env variables used

# this is the project containing the Cloud Source Repository
export PROJECT_CSR=my-csr-project
export CSR_REPO_NAME=my-repo
# this is the project running Cloud Build Job

Kernel and Network Tuning Consider tuning kernel and network and add this kind of following settings in /etc/sysctl.conf:

net.ipv4.tcp_max_syn_backlog = 40000
net.core.somaxconn = 40000
net.core.wmem_default = 8388608
net.core.rmem_default = 8388608
net.ipv4.tcp_sack = 1
net.ipv4.tcp_window_scaling = 1

	{
	"displayName": "Claude Code — daily cost per user over threshold",
	"documentation": {
	"content": "A user's Claude Code spend over the last 24h exceeded the configured threshold (default $50). Check the 'Cost Governance & Usage' dashboard, filter by the user in the incident labels, and review cost by model / query_source.",
	"mimeType": "text/markdown"
	},
	"combiner": "OR",
	"conditions": [
	{
	"displayName": "Cost per user over 24h > $50 (USD, Claude estimate)",

	#!/bin/bash

	set -e

	# Function to convert resources to milli format
	convert_to_m() {
	local value=$1
	case ${value: -1} in
	m) echo "${value%?}";;
	"") echo "$((value * 1000))";;

	#!/bin/bash

	# Function to redact sensitive fields within Secret objects
	redact_secrets() {
	secret_name=$1
	namespace=$2

	# Fields likely to contain sensitive information
	sensitive_fields=("data.password" "data.token" "stringData")

	apiVersion: v1
	kind: ServiceAccount
	metadata:
	name: httpbin
	---
	apiVersion: v1
	kind: Service
	metadata:
	name: httpbin
	labels:

	steps:

	- id: access remote docker registry
	name: 'gcr.io/cloud-builders/docker'
	entrypoint: 'bash'
	args: ['-c', 'docker login 10.1.0.5:5000 --username=$$USERNAME --password=$$PASSWORD']
	secretEnv: ['USERNAME', 'PASSWORD']

	- id: sync repo
	name: quay.io/skopeo/stable

	import os
	import json
	from flask import abort
	from google.cloud import pubsub_v1, error_reporting

	client = error_reporting.Client(project=os.getenv('GCP_PROJECT'))
	publisher = pubsub_v1.PublisherClient()
	topic_path = publisher.topic_path(os.getenv('GCP_PROJECT'), os.getenv('TOPIC_NAME'))

	def http2pubsub(request):

	#!/bin/bash

	APIURL=https://speech.googleapis.com
	REMOTEIP=$(curl -s ipinfo.io/ip)
	REMOTEASN=$(curl -s ipinfo.io/org \| cut -d' ' -f1)
	RESULTFILE="google-ping-api-results-$(date +%s).csv"

	## Script start time
	START=$(date +%s)