Update agent config: address review feedback from recent PRs#748
Update agent config: address review feedback from recent PRs#748
Conversation
There was a problem hiding this comment.
1 issue found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="self-development/kelos-pr-responder.yaml">
<violation number="1" location="self-development/kelos-pr-responder.yaml:90">
P2: Handle `KELOS_UPSTREAM_REPO` in the CI-check command, otherwise `gh pr checks` can target the wrong repo in upstream/fork workflows.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
self-development/agentconfig.yaml
Outdated
| - Logging conventions: start log messages with capital letters and do not end with punctuation | ||
| - Commit messages: do not include PR links in commit messages | ||
| - When making structural changes (adding new files, configs, or components), update related documentation (especially README files) to stay in sync | ||
| - When adding or changing API fields, also update self-development TaskSpawners (`self-development/*.yaml`) and example configs to use the new fields |
There was a problem hiding this comment.
Actually, it should be handled separately.
Remove it.
|
🤖 Kelos Task Status Task |
afa0333 to
d155925
Compare
|
/kelos needs-input All review feedback addressed — removed the "API changes require config updates" convention from |
gjkim42
left a comment
There was a problem hiding this comment.
Fix the review comments and squash commits
/kelos pick-up
AGENTS.md
Outdated
| - **Better tests.** Always try to add or improve tests(including integration, e2e) when modifying code. | ||
| - **Logging conventions.** Start log messages with capital letters and do not end with punctuation. | ||
| - **Commit messages.** Do not include PR links in commit messages. | ||
| - **API changes require config updates.** When adding or changing API fields, also update self-development TaskSpawners (`self-development/*.yaml`) and example configs to use the new fields. |
|
🤖 Kelos Task Status Task |
- Add KELOS_UPSTREAM_REPO to CI check commands in kelos-pr-responder - Require make verify and make test in re-review loops - Add Kubernetes resource.Quantity comparison convention - Active CI status checking instead of passive instruction Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
d155925 to
1a08a8a
Compare
|
/kelos needs-input All review feedback was addressed in previous commits (the "API changes require config updates" convention was already removed from both AGENTS.md and agentconfig.yaml). PR description updated to reflect the final diff. Ready for re-review. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Updates agent configuration based on review feedback from recent PRs:
Add
KELOS_UPSTREAM_REPOto CI check commands (kelos-pr-responder)gh pr checkscan target the wrong repo in upstream/fork workflows without--repo "$KELOS_UPSTREAM_REPO"Require
make verifyandmake testin re-review loops (kelos-pr-responder, kelos-workers)Add Kubernetes
resource.Quantitycomparison convention (AGENTS.md, agentconfig.yaml)reflect.DeepEqualmisdetected drift for equivalentresource.Quantityvalues because the struct has internal fields that differ for semantically identical quantities (e.g.,1000mvs1CPU). Adding this as a project convention to prevent recurrence.Which issue(s) this PR is related to:
N/A
Special notes for your reviewer:
All review feedback has been addressed:
agentconfig.yamlandAGENTS.mdper reviewer request (to be handled separately)Does this PR introduce a user-facing change?