Skip to content

Refine weekly claude command #759

Closed

Description

@PhilippMatthes

We implemented a new claude command under .claude/commands/weekly.md which performs a weekly code cleanup and checks the docs for any outdated material. For that purpose, the claude command utilizes a subagent for bug-checking and a subagent for docs refinement. This command should be refined a bit more.

Tasks

  1. It should be configurable how the subagents handle findings. Currently, they are instructed to directly open pull requests. However, this also means that the subagents cannot be directly used just to find issues without creating pull requests. This should be pulled out into the weekly command -> instructing the agents there to create pull requests with their findings.
  2. When pull requests are opened for bugs or documentation enhancements, it should be investigated which human contributors to the existing code/docs should be notified by assigning them to the created pull requests. Ideally, not everyone should be notified, only the most important contributors to the contents. This is to collect sign-offs from the right persons on the changes.
  3. Findings should be checked against open pull requests. If there is already an open pull request adressing the discovered issue(s), the finding should not be re-addressed.
  4. Instead of only creating 1 pull request per run, let the agents decide themselves which changes are important to cover. The agents need to reason over the importance. Keep in mind that all PRs need to be reviewed and merged by humans, so PR fatigue should be considered.
  5. Before any pull request is opened, agents need to verify make runs. Pull request titles must start with uppercase letters and conventional commits are not required (at the moment). The pull request content must be directly commitable as a concise commit message, so artificial linebreaks or markdown must be avoided.
  6. Agents should be instructed to read the AGENTS.md file before doing work.

Activity

  1. PhilippMatthes commented on Apr 26, 2026

    @PhilippMatthes
    MemberAuthor

    @claude can you adjust the commands and agents files under the .claude folder and open a pull request with your changes?

  2. sapcc-bot commented on Apr 26, 2026

    @sapcc-bot
    Contributor

    👋 Completed refining the weekly claude command and related agent files.

    Progress

    • Read and understand existing .claude/commands/weekly.md and agent files
    • Read AGENTS.md to understand project conventions
    • Refactor subagents to separate finding issues from creating PRs (Task 1)
    • Add logic for assigning relevant human contributors to PRs (Task 2)
    • Add deduplication against open PRs (Task 3)
    • Allow agents to decide which changes are important (Task 4)
    • Add make verification, PR title/content formatting rules (Task 5)
    • Instruct agents to read AGENTS.md before doing work (Task 6)
    • Commit changes and open a pull request

    Changes Made

    .claude/agents/bug-detective.md — Converted from a find-and-fix agent to a report-only agent. Removed Phase 2 (PR creation) and replaced it with importance reasoning. Output now returns structured findings with severity, suggested fixes, and key contributors instead of PR numbers. Added AGENTS.md setup step.

    .claude/agents/docs-expert.md — Same pattern: converted from find-and-fix to report-only. Removed Phase 2 (PR creation) and replaced with importance reasoning. Output now returns structured findings with priorities and key contributors. Added AGENTS.md setup step.

    .claude/commands/weekly.md — Major restructure from 3 phases to 7 phases:

    1. Setup — Read AGENTS.md
    2. Collect — Build weekly digest (unchanged)
    3. Collect open PRs — New phase for deduplication
    4. Dispatch — Send to subagents for investigation only (no PR creation)
    5. Deduplicate — Filter findings against open PRs, re-prioritize with PR fatigue guidance
    6. Create PRs — New phase: spawn dedicated subagents per fix with make verification, contributor assignment, and PR formatting rules
    7. Summarize — Enhanced report with dedup stats and backlog

    PR

    #760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions