Repository navigation
feat(deployment): Tier-based environment structure and container registry updates #501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
edee2b6
d1a5073
1f58e6a
abc6701
7ddfea9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| services: | ||
| hi-rag-gateway-v2-gpu: | ||
| image: ${HIRAG_V2_GPU_IMAGE:-ghcr.io/cataclysm-studios-inc/hi-rag-gateway-v2-gpu:cu128-py310-stable} | ||
| image: ${HIRAG_V2_GPU_IMAGE:-ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu:cu128-py310-stable} | ||
| runtime: nvidia | ||
|
Comment on lines
2
to
4
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: # Search for references to this image in the codebase
rg "hi-rag-gateway-v2-gpu" --type yml --type yaml -A 2 -B 2Repository: POWERFULMOVES/PMOVES.AI Length of output: 94 🏁 Script executed: # Look for any CI/CD, build, or deployment files that might reference image publishing
fd -e "yml" -e "yaml" -e "json" -e "dockerfile" -e "Dockerfile" | head -20Repository: POWERFULMOVES/PMOVES.AI Length of output: 929 🏁 Script executed: # Check the docker-compose file structure and any environment variable documentation
cat pmoves/docker-compose.gpu-image.ymlRepository: POWERFULMOVES/PMOVES.AI Length of output: 2208 🏁 Script executed: # Search for any documentation or scripts related to GPU image building/publishing
fd -e "md" -e "sh" -e "py" | xargs rg -l "HIRAG.*GPU|cu128|py310" 2>/dev/null | head -10Repository: POWERFULMOVES/PMOVES.AI Length of output: 348 🏁 Script executed: # Check the hi-rag-gateway-v2 documentation
cat pmoves/docs/services/hi-rag-gateway-v2/README.md | head -100Repository: POWERFULMOVES/PMOVES.AI Length of output: 6272 🏁 Script executed: # Search for GitHub Actions or CI/CD workflows
fd -e "yml" -e "yaml" | xargs rg -l "ghcr.io|gpu|image" | grep -i "workflow\|action\|ci\|\.github"Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Look for any GitHub Actions workflows
fd ".github" -type dRepository: POWERFULMOVES/PMOVES.AI Length of output: 237 🏁 Script executed: # Search for Dockerfile related to hi-rag-gateway-v2-gpu
fd -i "dockerfile*" | xargs grep -l "hi-rag-gateway\|cu128\|py310" 2>/dev/nullRepository: POWERFULMOVES/PMOVES.AI Length of output: 295 🏁 Script executed: # Search for any image build or publish scripts
rg "ghcr.io/powerfulmoves/hi-rag-gateway-v2-gpu" --type-list all -lRepository: POWERFULMOVES/PMOVES.AI Length of output: 456 🏁 Script executed: # Check the Dockerfile.gpu to see what organization it references
cat pmoves/services/hi-rag-gateway-v2/Dockerfile.gpuRepository: POWERFULMOVES/PMOVES.AI Length of output: 2244 🏁 Script executed: # Search for references to both organizations in the codebase
rg "cataclysm-studios-inc|powerfulmoves" --type yaml -B 2 -A 2Repository: POWERFULMOVES/PMOVES.AI Length of output: 6580 🏁 Script executed: # Look for any CI/CD workflows or build scripts that push images
fd -type f -name "*.yml" -o -name "*.yaml" | xargs grep -l "push\|build\|registry\|ghcr" 2>/dev/null | head -10Repository: POWERFULMOVES/PMOVES.AI Length of output: 237 🏁 Script executed: # Check if there are any recent commits or documentation about the image registry
rg "HIRAG_V2_GPU_IMAGE" -B 2 -A 2Repository: POWERFULMOVES/PMOVES.AI Length of output: 1412 Clarify the correct GHCR organization for the GPU image. The docker-compose file specifies 🤖 Prompt for AI Agents |
||
| restart: unless-stopped | ||
| env_file: [env.shared.generated, env.shared, .env.generated, .env.local] | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,8 @@ | ||
| # ============================================================================= | ||
| # PMOVES Agent Tier Environment Variables | ||
| # Services: agent-zero, archon, mesh-agent, supaserch, deepresearch, | ||
| # consciousness-service, archon-agent-work-orders, botz-gateway, | ||
| # publisher-discord, messaging-gateway, jellyfin-bridge, chat-relay | ||
| # ============================================================================= | ||
| # publisher-discord, messaging-gateway, jellyfin-bridge, chat-relay, | ||
| # github-runner-ctl | ||
|
|
||
| # Agent tier services handle orchestration and coordination | ||
| # They connect to internal services (Hi-RAG, NATS, Supabase) | ||
|
|
@@ -17,9 +16,9 @@ NATS_URL=nats://nats:4222 | |
| # --------------------------------------------------------------------------- | ||
| # Supabase (internal) | ||
| # --------------------------------------------------------------------------- | ||
| SUPABASE_URL=http://postgrest:3000 | ||
| SUPABASE_URL=http://supabase_kong_PMOVES.AI:8000 | ||
| SUPABASE_SERVICE_ROLE_KEY= # REQUIRED: From Supabase CLI | ||
| SUPA_REST_URL=http://postgrest:3000/rest/v1 | ||
| SUPA_REST_URL=http://supabase_kong_PMOVES.AI:8000/rest/v1 | ||
|
Comment on lines
+19
to
+21
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Search for docker-compose files and check for container name patterns
find . -type f \( -name "docker-compose*" -o -name "*.compose.yml" -o -name "*.compose.yaml" \) | head -20Repository: POWERFULMOVES/PMOVES.AI Length of output: 639 🏁 Script executed: # Search for supabase_kong container references in compose files
rg -n "supabase_kong" -A 2 -B 2 --type yamlRepository: POWERFULMOVES/PMOVES.AI Length of output: 2111 🏁 Script executed: # Also check for any references to the specific container name with dots
rg -n "supabase_kong_PMOVES\.AI" --type yamlRepository: POWERFULMOVES/PMOVES.AI Length of output: 666 🏁 Script executed: # Search for service definitions in docker-compose files - look for supabase services
rg -n "services:" -A 300 pmoves/docker-compose.yml | grep -A 50 "supabase"Repository: POWERFULMOVES/PMOVES.AI Length of output: 3983 🏁 Script executed: # Look for the supabase_kong service definition more specifically
rg -n "supabase_kong" -B 5 -A 5 pmoves/docker-compose.yml | head -50Repository: POWERFULMOVES/PMOVES.AI Length of output: 1740 🏁 Script executed: # Check if there's a network definition that might explain the naming
rg -n "networks:" -A 20 pmoves/docker-compose.ymlRepository: POWERFULMOVES/PMOVES.AI Length of output: 42643 🏁 Script executed: # Search for any service definition named supabase_kong
rg -n "supabase_kong:" pmoves/docker-compose.ymlRepository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Look for container_name or hostname definitions that might set this name
rg -n "container_name|hostname" pmoves/docker-compose.yml | grep -i supabaseRepository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Search across all compose files for supabase_kong service definition
find pmoves -name "docker-compose*.yml" -exec rg -l "supabase_kong:" {} \;Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Search for supabase_kong in all files and directories
find pmoves -type f \( -name "*.yml" -o -name "*.yaml" -o -name "*.env*" \) -exec rg -l "supabase_kong" {} \;Repository: POWERFULMOVES/PMOVES.AI Length of output: 128 🏁 Script executed: # Check if there's a separate supabase compose or configuration directory
ls -la pmoves/ | grep -i supabaseRepository: POWERFULMOVES/PMOVES.AI Length of output: 127 🏁 Script executed: # Search for any references that might explain this configuration
rg -n "supabase_kong_PMOVES\.AI" --type yaml --type txtRepository: POWERFULMOVES/PMOVES.AI Length of output: 666 🏁 Script executed: # Check contents of supabase directory
ls -la pmoves/supabase/Repository: POWERFULMOVES/PMOVES.AI Length of output: 351 🏁 Script executed: # Look for any service definition or configuration in supabase directory
find pmoves/supabase -type f \( -name "*.yml" -o -name "*.yaml" -o -name "*.json" -o -name "docker-compose*" \) | head -20Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Check if there's documentation or README about the supabase setup
find pmoves/supabase -name "README*" -o -name "*.md" | xargs cat 2>/dev/nullRepository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Check if postgrest service uses container_name or aliases that might explain the supabase_kong name
rg -n "postgrest" -B 5 -A 20 pmoves/docker-compose.yml | grep -A 20 "^postgrest:"Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Look for any network alias definitions that might create this hostname
rg -n "aliases:" -A 5 pmoves/docker-compose.ymlRepository: POWERFULMOVES/PMOVES.AI Length of output: 217 🏁 Script executed: # Check the env file referenced in the review to see if there's more context
cat -n pmoves/env.tier-agent | head -30Repository: POWERFULMOVES/PMOVES.AI Length of output: 1705 🏁 Script executed: # Check if there's any documentation about supabase setup or external service
find pmoves -name "*.md" -o -name "README*" | xargs grep -l "supabase_kong\|Kong\|gateway" 2>/dev/null | head -5Repository: POWERFULMOVES/PMOVES.AI Length of output: 384 🏁 Script executed: # Look for any instructions about external Supabase setup
find . -maxdepth 2 -name "*.md" | xargs grep -l "Supabase\|supabase" 2>/dev/nullRepository: POWERFULMOVES/PMOVES.AI Length of output: 518 🏁 Script executed: # Verify the complete context of postgrest service definition
rg -n "postgrest:" -A 30 pmoves/docker-compose.yml | head -50Repository: POWERFULMOVES/PMOVES.AI Length of output: 1776 🏁 Script executed: # Search for any Kong service or gateway configuration
rg -n "kong" -i pmoves/docker-compose.ymlRepository: POWERFULMOVES/PMOVES.AI Length of output: 421 🏁 Script executed: # Check if there's documentation about external Supabase or Kong setup
cat ./README.md | grep -A 10 -B 2 -i "supabase\|kong" | head -40Repository: POWERFULMOVES/PMOVES.AI Length of output: 5412 🏁 Script executed: # Look for any env file that might have the actual service definition
find pmoves -name "env*" -type f | xargs grep -l "supabase_kong" 2>/dev/nullRepository: POWERFULMOVES/PMOVES.AI Length of output: 118 🏁 Script executed: # Check the Supabase service documentation
cat pmoves/docs/services/supabase/README.md 2>/dev/null | head -100Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Check the env example file to see if there's guidance
cat pmoves/env.tier-agent.example | head -30Repository: POWERFULMOVES/PMOVES.AI Length of output: 1577 🏁 Script executed: # Check if there's documentation about Supabase CLI setup
grep -r "supabase start\|supabase_kong\|Kong gateway" pmoves/docs/ 2>/dev/null | head -20Repository: POWERFULMOVES/PMOVES.AI Length of output: 2018 🏁 Script executed: # Look at the main README for Supabase setup instructions
cat pmoves/README.md 2>/dev/null | grep -A 20 -B 5 -i "supabase\|kong" | head -60Repository: POWERFULMOVES/PMOVES.AI Length of output: 49 🏁 Script executed: # Check the LOCAL_TOOLING_REFERENCE mentioned in main README
cat pmoves/docs/LOCAL_TOOLING_REFERENCE.md 2>/dev/null | grep -A 10 -B 2 -i "supabase\|kong\|port 8000" | head -50Repository: POWERFULMOVES/PMOVES.AI Length of output: 9863 🏁 Script executed: # Verify the correct Supabase internal hostname from documentation
cat pmoves/docs/LOCAL_TOOLING_REFERENCE.md | grep -A 5 -B 5 "api.supabase.internal"Repository: POWERFULMOVES/PMOVES.AI Length of output: 2585 🏁 Script executed: # Check if there are any recent changes or PRs related to supabase_kong
git log --oneline -20 -- pmoves/env.tier-agent pmoves/docker-compose.yml 2>/dev/null | head -10Repository: POWERFULMOVES/PMOVES.AI Length of output: 149 🏁 Script executed: # Verify what the actual Supabase CLI provides
grep -r "api.supabase\|supabase.internal" pmoves/docs/ pmoves/*.md 2>/dev/nullRepository: POWERFULMOVES/PMOVES.AI Length of output: 2033 Correct the Supabase URL hostname to match the documented standard. The hostname This matches the established pattern for compose-based Supabase networking and will resolve DNS correctly inside Docker containers on the 🤖 Prompt for AI Agents |
||
|
|
||
| # --------------------------------------------------------------------------- | ||
| # Hi-RAG Gateway (internal) | ||
|
|
@@ -50,7 +49,7 @@ AGENTZERO_JETSTREAM=true | |
| # --------------------------------------------------------------------------- | ||
| ARCHON_SERVER_PORT=8091 | ||
| ARCHON_MCP_PORT=8051 | ||
| ARCHON_SUPABASE_BASE_URL=http://postgrest:3000 | ||
| ARCHON_SUPABASE_BASE_URL=http://supabase_kong_PMOVES.AI:8000 | ||
|
|
||
| # --------------------------------------------------------------------------- | ||
| # DeepResearch Settings | ||
|
|
@@ -65,3 +64,12 @@ DEEPRESEARCH_NOTEBOOK_EMBED=true | |
| # --------------------------------------------------------------------------- | ||
| DISCORD_WEBHOOK_URL= # Optional: Discord webhook for notifications | ||
|
|
||
| # --------------------------------------------------------------------------- | ||
| # GitHub Runner Controller (CI/CD orchestration) | ||
| # --------------------------------------------------------------------------- | ||
| GITHUB_RUNNER_CTL_PORT=8100 | ||
| GITHUB_RUNNER_CTL_WEB_PORT=8104 | ||
| GITHUB_RUNNER_CTL_LOG_LEVEL=INFO | ||
| GITHUB_REPOSITORIES=POWERFULMOVES/PMOVES.AI | ||
| GITHUB_RUNNER_REFRESH_INTERVAL=60 | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -4,28 +4,31 @@ | |||||||||||||
| # Services: postgres, qdrant, neo4j, meilisearch, minio, nats | ||||||||||||||
| # Scope: Infrastructure credentials ONLY (no external API keys) | ||||||||||||||
| # | ||||||||||||||
| # Copy to `env.tier-data` and fill in real values. The file is gitignored. | ||||||||||||||
| # Fill in real values below. This file is gitignored. | ||||||||||||||
| # ============================================================================= | ||||||||||||||
|
|
||||||||||||||
| # PostgreSQL (pgvector) | ||||||||||||||
| # Used by: postgres service, all services that query Supabase/PostgREST | ||||||||||||||
| POSTGRES_DB=pmoves | ||||||||||||||
| POSTGRES_USER=pmoves | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -base64 24` | ||||||||||||||
| POSTGRES_PASSWORD=A7sX9kL2mN4pQ8rT6vW3yZ5bC1dE8fG0hJ2 | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -base64 24` for production deployments | ||||||||||||||
| # For development, a safe default is provided | ||||||||||||||
| POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-pmoves_dev} | ||||||||||||||
|
Comment on lines
+14
to
+16
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shell variable expansion won't work in Docker Compose Docker Compose's 🐛 Proposed fixFor dev defaults, either: Option 1: Use literal default value (recommended for dev env file): -POSTGRES_PASSWORD=${POSTGRES_PASSWORD:-pmoves_dev}
+POSTGRES_PASSWORD=pmoves_devOption 2: Leave empty and set defaults in environment:
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-pmoves_dev}📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||
|
|
||||||||||||||
| # Neo4j (Knowledge Graph) | ||||||||||||||
| # Format: neo4j/<password> | ||||||||||||||
| # REQUIRED: Generate password with `openssl rand -base64 24` | ||||||||||||||
| NEO4J_AUTH=neo4j/7kJtbpJ1n1xzMX4F2EAu60K5 | ||||||||||||||
| # REQUIRED: Generate password with `openssl rand -base64 24` for production deployments | ||||||||||||||
| # For development, use "neo4j/none" to disable auth (healthcheck compatibility) | ||||||||||||||
| NEO4J_AUTH=neo4j/none | ||||||||||||||
|
|
||||||||||||||
| # Meilisearch (Full-text Search) | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -hex 32` | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -hex 32` for production deployments | ||||||||||||||
| MEILI_MASTER_KEY= | ||||||||||||||
|
|
||||||||||||||
| # MinIO (S3-compatible Object Storage) | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -base64 32` | ||||||||||||||
| # REQUIRED: Set unique username for production deployments | ||||||||||||||
| MINIO_ROOT_USER= | ||||||||||||||
| # REQUIRED: Generate with `openssl rand -base64 32` for production deployments | ||||||||||||||
| MINIO_ROOT_PASSWORD= | ||||||||||||||
|
|
||||||||||||||
| # Qdrant (Vector Database) | ||||||||||||||
|
|
||||||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,15 +7,17 @@ NATS_URL=nats://nats:4222 | |
|
|
||
| # ----- MinIO (Media Storage) ----- | ||
| MINIO_ENDPOINT=minio:9000 | ||
| MINIO_ACCESS_KEY=minioadmin | ||
| MINIO_SECRET_KEY=minioadmin | ||
| # REQUIRED: Set unique access key for production deployments | ||
| MINIO_ACCESS_KEY= | ||
| # REQUIRED: Generate with `openssl rand -base64 32` for production deployments | ||
| MINIO_SECRET_KEY= | ||
| MINIO_SECURE=false | ||
| MINIO_BUCKET=assets | ||
| MINIO_OUTPUT_BUCKET=outputs | ||
|
|
||
| # ----- Supabase (Metadata) ----- | ||
| SUPA_REST_URL=http://host.docker.internal:65421/rest/v1 | ||
| SUPABASE_SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.fake_key_replace_with_real | ||
| SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here | ||
|
|
||
|
Comment on lines
9
to
21
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Empty placeholders can override layered env values. 🔧 Safer placeholder pattern-# REQUIRED: Set unique access key for production deployments
-MINIO_ACCESS_KEY=
-# REQUIRED: Generate with `openssl rand -base64 32` for production deployments
-MINIO_SECRET_KEY=
+## REQUIRED: Set unique access key for production deployments
+# MINIO_ACCESS_KEY=
+## REQUIRED: Generate with `openssl rand -base64 32` for production deployments
+# MINIO_SECRET_KEY=
@@
-SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here
+# SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here🤖 Prompt for AI Agents |
||
| # ----- PMOVES.YT ----- | ||
| YT_CHANNEL_CHECK_INTERVAL=3600 | ||
|
|
@@ -32,7 +34,3 @@ FRAME_SAMPLE_RATE=5 | |
|
|
||
| # ----- Indexer Namespace ----- | ||
| INDEXER_NAMESPACE=pmoves | ||
|
|
||
| # ----- Invidious (from GitHub Secrets in production) ----- | ||
| INVIDIOUS_HMAC_KEY=temp_test_key_please_replace_from_gh_secrets | ||
| INVIDIOUS_COMPANION_KEY=temp_test_key_please_replace_from_gh_secrets | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 85
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 244
🏁 Script executed:
Repository: POWERFULMOVES/PMOVES.AI
Length of output: 445
🏁 Script executed:
# Read the .coderabbit.yaml file with line numbers cat -n ./.coderabbit.yamlRepository: POWERFULMOVES/PMOVES.AI
Length of output: 1106
🌐 Web query:
CodeRabbit .coderabbit.yaml schema configuration documentation💡 Result:
Here are the official CodeRabbit docs for the .coderabbit.yaml schema and configuration:
Key points: place .coderabbit.yaml in the repository root; the docs include example files and the machine-readable JSON schema (referenced in examples as yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json). [2][1]
Sources:
🌐 Web query:
CodeRabbit schema json https://coderabbit.ai/integrations/schema.v2.json documentation review top-level keys💡 Result:
Top-level keys in the CodeRabbit schema (schema.v2.json) and brief descriptions:
Source: CodeRabbit schema JSON. [1] https://coderabbit.ai/integrations/schema.v2.json
🌐 Web query:
CodeRabbit configuration pre_merge_checks docstrings threshold💡 Result:
Short answer: CodeRabbit’s pre_merge_checks include a Docstring Coverage check with a configurable "threshold" (percentage). The default threshold is 80% and you can set it in .coderabbit.yaml under reviews.pre_merge_checks.docstrings.threshold (example: threshold: 85). You can also set the check’s mode (off | warning | error). [1][2]
Sources:
documentationandrevieware invalid top-level keys in CodeRabbit schema.Per the official CodeRabbit schema (schema.v2.json), valid top-level keys are
reviews,pre_merge_checks,language,tone_instructions,early_access,enable_free_tier,inheritance, andfinishing_touches. Thedocumentationandreviewblocks at lines 20–36 will be ignored.Move documentation coverage to
pre_merge_checks.docstrings.thresholdand keep review settings nested within thereviewsblock:🔧 Schema-aligned adjustment
reviews: review_status: true branches: - "PMOVES.AI-Edition-Hardened" - "PMOVES.AI-Edition-Hardened-v3-clean" - "feat/hardened-*" - "fix/hardened-*" excluded_branches: - "main" - "origin/main" + num_commits: 10 + summary: true + line_comments: true -# Documentation comment requirements -documentation: - # Require docstrings for Python functions/classes - coverage: - minimum: 80 - patch: 80 - -# Review depth settings -review: - # Number of commits to review in a PR - num_commits: 10 - - # Include summary of PR - summary: true - - # Enable line-by-line reviews - line_comments: true + +pre_merge_checks: + docstrings: + threshold: 80🤖 Prompt for AI Agents