Skip to content

Configuration Alignment: Inline AgentConfigs missing conventions from CLAUDE.md and shared agentconfig.yaml #776

@kelos-bot

Description

@kelos-bot

🤖 Kelos Self-Update Agent @gjkim42

Problem

Inline AgentConfigs defined in TaskSpawner YAML files have drifted from both CLAUDE.md and the shared self-development/agentconfig.yaml. This means different agents operate under different subsets of project conventions, leading to inconsistent behavior.

Findings

1. Conventions present in shared agentconfig.yaml but missing from inline AgentConfigs

The shared agentconfig.yaml (kelos-dev-agent) includes two conventions not present in most inline AgentConfigs:

  • "Kubernetes resource comparison" — present in agentconfig.yaml line 33, missing from: kelos-workers-agent, kelos-fake-strategist-agent, kelos-fake-user-agent, kelos-self-update-agent, kelos-image-update-agent
  • "When making structural changes, update related documentation" — present in agentconfig.yaml line 32, missing from ALL inline AgentConfigs

2. Reviewer AgentConfig missing make update from Makefile targets

kelos-reviewer-agent lists Makefile targets but omits make update:

# Current (kelos-reviewer.yaml lines 23-28):
    - Use Makefile targets instead of discovering build/test commands yourself:
      - `make verify` — ...
      - `make test` — ...
      - `make test-integration` — ...
      - `make build` — ...
      # missing: make update

The reviewer prompt itself references make update artifacts (line 127: "if API types or CRDs changed, were make update artifacts included?"), but the AgentConfig doesn't list it as an available target. This is inconsistent and could confuse the agent.

3. CLAUDE.md PR conventions missing from all AgentConfigs

CLAUDE.md has an entire "Pull Requests" section with conventions critical for PR-creating agents:

  • Always follow .github/PULL_REQUEST_TEMPLATE.md when creating PRs
  • Fill in every section of the template (use "N/A" or "NONE" where appropriate)
  • Choose exactly one /kind label from: bug, cleanup, docs, feature
  • /kind cleanup for PRs that only modify self-development/ files
  • Release-note guidance: write "NONE" for non-user-facing changes, meaningful notes for API/CRD changes

None of these conventions appear in any AgentConfig. The PR-creating agents affected are:

  • kelos-workers-agent (creates PRs for issues)
  • kelos-dev-agent shared config (used by kelos-pr-responder, kelos-config-update)
  • kelos-image-update-agent (the prompt references the PR template, but the AgentConfig doesn't)

4. CLAUDE.md rules missing from all AgentConfigs

These CLAUDE.md conventions are not in any AgentConfig:

  • "For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML"
  • "e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead"
  • Directory structure (cmd/, test/e2e/, .github/workflows/)

Proposed Fix

  1. Add the missing conventions to all inline AgentConfigs that create PRs or modify code (workers, self-update, config-update via shared config)
  2. Add make update to the reviewer AgentConfig's Makefile targets list
  3. Add the PR conventions section from CLAUDE.md to AgentConfigs used by PR-creating agents
  4. Add the "e2e tests" and "CI/release workflows" conventions to coding agents

Related Issues

This issue covers the broader pattern of convention drift across all inline AgentConfigs, not just individual agents.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions