CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-agents-docs

Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/sync-agents-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Sync Documentation After Build Changes

This is a manual checklist — disable-model-invocation: true means agents cannot execute it autonomously. Human developers should walk through this after buildSrc changes.

After modifying buildSrc or build conventions, check whether AGENTS.md files, skills, and references need updating. Review your changes against the checklist below and update only the affected files.

Checklist

What changedWhat to update
Formatting conventions (spotless.gradle.kts)Root AGENTS.md Style section, style-reference reference, affected module AGENTS.md files
Convention plugins added or removedbuildSrc/AGENTS.md plugin table, root AGENTS.md if build commands or workflow changed
Testing conventions (testing-*.gradle.kts)Root AGENTS.md Testing section, testing-guide reference, affected module AGENTS.md files
Project plugins added or removedbuildSrc/AGENTS.md project plugin table
Build commands or task names changedRoot AGENTS.md Build and Before Submitting sections, evergreen skill, module AGENTS.md files
CI/CD or publishing changesevergreen skill

How to use

  1. Review the diff of your buildSrc changes
  2. Walk through the checklist above — only rows matching your changes need action
  3. Update the affected files, keeping changes minimal and accurate
  4. Verify no stale references remain (e.g., renamed tasks, removed plugins)
Repository
mongodb/mongo-java-driver
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.