Skip to content

feat(team-agents): add effort level to all sub-agents#66

Merged
duyet merged 2 commits into
masterfrom
feat/team-agents-effort-levels
May 14, 2026
Merged

feat(team-agents): add effort level to all sub-agents#66
duyet merged 2 commits into
masterfrom
feat/team-agents-effort-levels

Conversation

@duyet

@duyet duyet commented May 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add effort frontmatter field to all 6 team-agent sub-agents to control reasoning depth per role
  • leader, senior-engineer, deep-research-agent → high (complex decisions, thorough analysis)
  • performance-engineer, python-expert → medium (focused specialist work)
  • junior-engineer → low (speed-first execution on clear specs)
  • Bump plugin version 1.7.0 → 1.8.0

Test plan

  • Verify agent frontmatter parses correctly in Claude Code
  • Confirm effort levels are applied when agents are spawned

Summary by Sourcery

Add configurable effort levels to all team-agent roles to control reasoning depth and update plugin metadata accordingly.

New Features:

  • Introduce an effort frontmatter field to all team-agent sub-agents to represent their reasoning depth tiers (high, medium, low).

Enhancements:

  • Configure appropriate effort levels for leader, senior-engineer, deep-research-agent, performance-engineer, python-expert, and junior-engineer agents.

Set reasoning effort budgets aligned with each agent's role:
leader/senior-engineer/deep-research → high, performance-engineer/python-expert → medium, junior-engineer → low.

Bump version 1.7.0 → 1.8.0.

Co-Authored-By: duyetbot <duyetbot@users.noreply.github.com>
@sourcery-ai

sourcery-ai Bot commented May 14, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Add an effort frontmatter field to all team-agent sub-agents to control reasoning depth per role, and bump the team-agents Claude plugin version from 1.7.0 to 1.8.0.

File-Level Changes

Change Details Files
Introduce an effort frontmatter field across all team-agent role definitions to standardize reasoning depth configuration per agent.
  • Add effort: high to leader, senior-engineer, and deep-research-agent frontmatter blocks.
  • Add effort: medium to performance-engineer and python-expert frontmatter blocks.
  • Add effort: low to junior-engineer frontmatter block.
team-agents/agents/deep-research-agent.md
team-agents/agents/junior-engineer.md
team-agents/agents/leader.md
team-agents/agents/performance-engineer.md
team-agents/agents/python-expert.md
team-agents/agents/senior-engineer.md
Update the team-agents Claude plugin manifest version to reflect the new effort-level configuration capability.
  • Bump plugin version from 1.7.0 to 1.8.0 in the plugin manifest.
team-agents/.claude-plugin/plugin.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions

Copy link
Copy Markdown

Welcome! 👋

Thank you for your first contribution to this project! We appreciate you taking the time to improve our codebase.

Next Steps

  • A maintainer will review your PR shortly
  • Please check for any review comments and address them
  • Feel free to ask questions if anything is unclear

Contribution Guidelines

  • Ensure all tests pass
  • Update documentation if needed
  • Keep changes focused and atomic

Thanks again for contributing! 🎉

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@coderabbitai

coderabbitai Bot commented May 14, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@duyet has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 16 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: cb66c851-9c9e-4948-91bc-af3b42980212

📥 Commits

Reviewing files that changed from the base of the PR and between 6fc6a56 and 7451a60.

📒 Files selected for processing (8)
  • team-agents/.claude-plugin/plugin.json
  • team-agents/.codex-plugin/plugin.json
  • team-agents/agents/deep-research-agent.md
  • team-agents/agents/junior-engineer.md
  • team-agents/agents/leader.md
  • team-agents/agents/performance-engineer.md
  • team-agents/agents/python-expert.md
  • team-agents/agents/senior-engineer.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/team-agents-effort-levels

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Co-Authored-By: duyetbot <duyetbot@users.noreply.github.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the plugin version to 1.8.0 and introduces an effort metadata field across various agent definitions to control reasoning depth. Feedback indicates that the effort parameter is currently incompatible with the opus and haiku models used by the leader and junior-engineer agents, as these models do not support the reasoning/thinking feature, rendering the new configuration ineffective for those specific agents.

name: leader
description: Coordinate complex tasks by breaking requirements into parallel workstreams, delegating to senior-engineer agents, and ensuring quality.
model: opus
effort: high

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The effort field is used to control reasoning depth (thinking), which is a feature currently supported by Claude 3.7 Sonnet. Since this agent is explicitly configured to use model: opus (line 4), the effort: high setting will be ignored as Opus does not support the thinking parameter. To achieve the intended high-depth reasoning for the leader role, consider updating the model to sonnet. This will also likely improve response quality and reduce latency compared to Opus.

name: junior-engineer
description: Execute well-defined tasks with blazing speed and precision. Specializes in implementation from clear specifications. Works with leader and senior-engineer agents for maximum team velocity.
model: haiku
effort: low

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The effort parameter is not supported by the haiku model. While low effort aligns with the agent's goal of 'blazing speed', the parameter will be ignored by the model. If you intend to use reasoning depth control, a compatible model like sonnet would be required, though haiku remains an appropriate choice for simple, fast execution tasks where reasoning is not the priority.

@duyet duyet merged commit ccba44d into master May 14, 2026
3 checks passed
@duyet duyet deleted the feat/team-agents-effort-levels branch May 14, 2026 15:39

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d7f7d6e7c4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"name": "team-agents",
"description": "Leader and Senior Engineer agents for coordinated parallel task execution. Leader breaks down complex tasks and delegates to multiple senior engineers working in parallel.",
"version": "1.7.0",
"version": "1.8.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep Claude and Codex manifest versions in sync

Bumping only the Claude manifest to 1.8.0 introduces a cross-manifest version mismatch because team-agents/.codex-plugin/plugin.json remains at 1.7.0. The repository’s validation (scripts/validate-plugins.sh, validate_cross_manifest) now fails with team-agents: version differs between Claude and Codex manifests, which can block CI/release workflows that enforce manifest parity.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant