build: being even more explicit about loading scripts
CI / benchmark-regression (push) Failing after 0s
CI / benchmark-publish (push) Failing after 0s
CI / push-validation (push) Successful in 26s
CI / helm (push) Successful in 30s
CI / build (push) Successful in 3m51s
CI / lint (push) Successful in 4m4s
CI / quality (push) Successful in 4m27s
CI / typecheck (push) Successful in 4m43s
CI / security (push) Successful in 4m45s
CI / integration_tests (push) Successful in 6m51s
CI / e2e_tests (push) Successful in 7m23s
CI / unit_tests (push) Successful in 8m51s
CI / docker (push) Failing after 44s
CI / coverage (push) Successful in 14m47s
CI / status-check (push) Failing after 4s

This commit is contained in:
2026-04-17 18:26:54 -04:00
parent 37402e83c2
commit bcf58f0703
+1 -1
View File
@@ -55,7 +55,7 @@ You are a supervisor that monitors open PRs for merge readiness, verifies all cr
**Always** do the following things first before anything else: **Always** do the following things first before anything else:
- Load the `auto-agents-system` skill and from it learn how to use the scripts with the following names: `list_prs_ready_to_merge`, `list_prs_stale_clean`, `list_prs_stale_conflicts`, `list_prs_needs_review_stale_clean`, and `list_prs_needs_review_stale_conflicts`. - Load the `auto-agents-system` skill and from it learn how to use the scripts with the following names: `list_prs_ready_to_merge`, `list_prs_stale_clean`, `list_prs_stale_conflicts`, `list_prs_needs_review_stale_clean`, and `list_prs_needs_review_stale_conflicts`. Once you have queried the skill to fully understand these scripts you should understand what arguments it takes, what arguments are valid, how to call it, and what output you expect in return.
## What You Receive ## What You Receive