Repository navigation
docs(agents): add steward skill for driving PRs to green - #975
Merged
Merged
Conversation
Repo-specific guidance an agent reads before acting on CI or review events: squash-merge to develop, local verification limits (JDK 8/24/28 toolchains), golden-data regeneration, CI failure signatures seen on dependency PRs, and the rule that Renovate failures are fixed at the root in a separate PR instead of on renovate/* branches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013d3caXQCpuNvgTAwpJMYqK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change do?
Adds
.claude/skills/steward/SKILL.md. It is repo-specific guidance that a Claude Code agent reads before it acts on CI results or review comments on a PR it is driving. It is also an ordinary invocable skill for Claude Code sessions in this repo. It links toAGENTS.mdinstead of repeating it, and covers:developand are squash-merged with Conventional Commits titles. The agent's own branches takedevelopin with a merge commit, and are not force-pushed after review.spotlessCheckand the tests of changed modules.common.gradle), JDK 24 (thejava24source set) and JDK 28 (classFileApiBackendTest). When one is missing, say so in the PR's Testing section instead of ticking the box.-PupdateTestData.429gets one re-run at most.renovate/*branches. Renovate force-rebases them, anddependency-auto-merge.ymlwould auto-merge the agent's commit under the bot's approval.develop: a Renovate rule for an intentional pin, or the code changes a wanted upgrade needs.Related issue
N/A. Follow-up to #974.
Scope and compatibility
Compatibility or migration notes:
Adds one agent-guidance file. No build or runtime change.
Testing
spotlessCheck(N/A: no Java sources)Commands and results:
I checked the facts the skill states against the repo:
common.gradle:22resolves the JDK 8 compiler eagerly.btrace-agent/build.gradle:38sets the JDK 24 toolchain, and:184the JDK 28 launcher, withcheck.dependsOn classFileApiBackendTest..github/workflows/dependency-auto-merge.ymlapprovesrenovate[bot]PRs and merges them afterBTrace CI/CDandCodeQLpass.develophistory consists of(#NNN)squash commits.Documentation and release impact
Release notes / follow-up work:
The skill's Spotless line works whether or not #974 has merged. Two conventions are worth confirming before merge, because they reflect what I observed rather than a written rule: merge-commit updates on the agent's own branches, and squash-merge as the norm.
Final checklist
Generated by Claude Code
This change is