Example agents
We are releasing a series of example agents that you can extend for your own use-cases. These example agents are shared via the public Bitbucket repository.
注意:
Several example agents require Rovo Dev sub-agents in order to function correctly.
Rovo Dev sub-agents need to be placed in a specific directory within the repo (
/.rovodev).The repository containing the example agents contains a
.rovodevdirectory in the root of the directory containing the required sub-agents for the examples.We recommend copying this
.rovodevdirectory into any repository where you are planning to implement one of the example agents.
Available Use Cases
1. README Auto-Updater
Automatically update project documentation based on code changes.
Trigger: Scheduled (e.g., weekly) or manual
What It Does: Analyzes code, extracts API docs, updates README with current state
Best For: Services with REST APIs that need accurate documentation
2. Checkstyle Auto-Fixer
Automatically detect and fix Java code style violations.
Trigger: Push to non-main branches
What It Does: Detects Checkstyle violations, applies automatic fixes, creates PR
Best For: Java projects that want consistent code style without manual effort
3. PR Summary Generator
Automatically generate comprehensive summaries for pull requests.
Trigger: Pull request creation/update
What It Does: Analyzes PR changes, groups by intent, generates impact/risk assessment
Best For: Teams that want faster, more focused code reviews (especially for large PRs)
4. Feature Flag Cleaner
Automatically remove feature flags by consolidating code paths to GA behavior.
Trigger: Manual (with FEATURE_GATE variable)
What It Does: Removes flag definition, consolidates to enabled behavior, updates tests, verifies with compile/test/checkstyle
Best For: Teams with feature flags that need thorough cleanup after rollout
5. Release Notes Generator
Automatically generate comprehensive release notes based on git history between version changes.
Trigger: Version change in
version.txtor manual executionWhat It Does: Analyzes commits between versions, categorizes changes, generates structured release notes with PR creation
Best For: Teams that want automated, comprehensive release documentation
6. Security Scanner
Automatically identify and fix security vulnerabilities in Java code and Maven dependencies.
Trigger: Manual execution or integration with security scanning pipelines
What It Does: Analyzes Snyk reports, updates vulnerable dependencies, fixes code security issues, creates PR with fixes
Best For: Teams that want automated security vulnerability remediation with verification
6. Codecoverage analyzer
Automatically analyze codecoverage on the project and suggest improvements by adding new tests.
Trigger: Manual execution or integration with PR based pipelines.
What It Does: Analyzes codecoverage on the project and suggests improvements by adding new tests and creates PR with fixes.
Best For: Teams that want to track and improve codecoverage automatically.
この内容はお役に立ちましたか?