القائمة
When adding or changing files under infra/k8s/ or sync targets for k8s, know what Argo CD syncs and remind the user to push to Git so the cluster can sync.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
When changing API routes, auth, or env-dependent behavior, add or update the corresponding integration tests and keep the test file layout consistent.
Keeps tools/generate-data seeders and docs in sync when main or management DB schema or ORM entities change. Use when adding or changing tables/entities in packages/orm, packages/management-orm, or infra database migrations.
When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code.
Use when adding or changing environment variables, infra/env/classification YAML, scripts/env-classification, K8s env render, or local env generation.
Common patterns for the Boilerplate HTTP API (Express)
When adding or changing preconditions, cleanup steps, or env usage for local Docker Compose or local k3d, keep both in sync where they share resources (e.g. infra/config/local/*.env).
| name | argocd-gitops-push |
| description | When adding or changing files under infra/k8s/ or sync targets for k8s, know what Argo CD syncs and remind the user to push to Git so the cluster can sync. |
When adding or changing files under:
infra/k8s/ (local, base, or app-of-apps manifests and referenced resources),infra/k8s/local/apps, infra/k8s/local/stack, infra/k8s/base/stack, postgres-init under base, and files referenced by those via Kustomize),infra/k8s/base/stack/postgres-init/0003_app_schema.sql and 0005_management_schema.sql.frag from scripts/database/combine-migrations.sh; make sync_k8s_postgres_init copies stack → base/db/postgres-init/ for Kustomize).infra/k8s/local/apps (see infra/k8s/local-application.yaml), which references infra/k8s/local/stack and the base stack.develop) is used; the agent does not push. The user must push for Argo CD to see changes.Any change to files under those paths (or to canonical sources that get copied into them) means the cluster will not reflect the change until the user pushes to the branch Argo CD tracks.
When your file-modifying work touches any of these paths, add a short Push to Git note in the response (e.g. before or after the verification block):
Push to Git: This change affects Argo CD–synced manifests. Push to the branch Argo CD tracks (e.g. develop) for the cluster to sync.