Files
stonks-oracle/.kiro/hooks/phase-commit.md
T
Celes Renata ebea70573b phase 0+1: project scaffold, k8s manifests, CI pipeline, steering, hooks, tests
- Repository structure for all services, infra, lakehouse, dashboards
- K8s manifests targeting stonks-oracle namespace with GHCR images
- Ingress via Traefik with ca-issuer TLS for internal services
- ConfigMap wired to existing cluster services (pg, redis, minio, ollama)
- GitHub Actions workflow for lint, test, multi-service container builds
- Dockerfile with build-arg CMD per service
- Makefile for local build/push/deploy
- Steering rules for TDD workflow, K8s conventions, project context
- Agent hooks for lint-on-save, test-on-save, k8s-validate, phase-commit
- Ruff linter config, all lint issues fixed
- 14 passing tests for schemas, config, redis keys
- PostgreSQL migrations, Trino catalogs, Superset config, MinIO lifecycle
2026-04-11 03:25:08 -07:00

414 B

name, description, version, trigger
name description version trigger
Phase Commit and Push Commit and push after completing a spec phase task 1.0
type
manual

When triggered manually after completing a phase:

  1. Run git add -A
  2. Ask the user for a commit message, suggesting format: phase N: short description
  3. Run git commit -m "{message}"
  4. Run git push origin main
  5. Report the commit SHA and confirm push succeeded