agentleFS
btraceiobtraceio/btrace/.agents/skills/steward/SKILL.md

steward

Skill6k starsChanged 2 days agoApache-2.0View on GitHub

BTrace conventions for driving a pull request to green — CI triage, review follow-up, dependency-bot (Renovate) PRs, and what to verify before pushing. Use when watching, fixing, or shepherding a PR in this repository.

19 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 3 mentionsOct 2026: 2 mentionsNov 2026: 3 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the btraceio/btrace repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about btraceio/btrace

The biggest 5 of 25 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 25

Talked about on GitHub and Stack Overflow (25 times).

On GitHub · 19

14 more on GitHub

Used with

Projects with it also use release.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run what the change can affect: spotlessCheck and the changed modules' tests, with output redirected to a log as AGENTS.md describes.

    line 17
  2. Very specific:

    Do not push to renovate/* branches.

    line 32
  3. Very specific:

    When a bot PR fails, find the root cause and fix it in a separate PR from develop:

    line 33

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stewarding a BTrace pull request

Repository rules in AGENTS.md apply throughout; this file adds only what is specific to driving a PR.

Branches and merging

  • PRs target develop. They are squash-merged, so the PR title becomes the commit subject: use a Conventional Commits title (fix(agent): ..., build: ..., chore(deps): ...).
  • On a branch you created, bring develop in with a merge commit once the PR is open; do not force-push a branch a reviewer has already looked at.

Before every push

  • Run what the change can affect: spotlessCheck and the changed modules' tests, with output redirected to a log as AGENTS.md describes.
  • Configuring the root build needs a JDK 8 toolchain (common.gradle resolves it eagerly), and btrace-agent needs a JDK 24 toolchain to compile its java24 source set and a JDK 28 launcher for classFileApiBackendTest, which check depends on. If a required JDK is unavailable locally, Gradle cannot verify the change: say so in the PR's Testing section instead of ticking the box, and treat the PR's CI as the check.
  • Golden instrumentation data in btrace-agent/src/test/resources/instrumentorTestData/ is regenerated only with ./gradlew test -PupdateTestData, and only for an intentional instrumentation change. Never edit it by hand, and never regenerate it to make an unexplained diff go away.

CI triage

  • spotlessCheck failing on files the PR did not touch means the formatter changed, not the code. gradle/spotless.gradle pins googleJavaFormat('1.30.0') because an unpinned one follows the Spotless plugin's default and a Spotless bump can move it; check whether that pin or the Spotless plugin version moved before running spotlessApply across the tree.
  • Cannot find a Java installation ... matching: {languageVersion=N} means a workflow no longer installs a JDK the build needs. The setup-java steps in .github/workflows/ are toolchain requirements (JDK 24 feeds btrace-agent's java24 source set); restore the step rather than changing the build.
  • JUnit resolving a JDK 17+ artifact for a JVM 8 configuration means the JUnit 5.14.4 pin was bumped. btrace-agent and integration-tests compile tests with a JDK 8 javac, and btrace-gradle-plugin keeps Java 8-compatible test dependencies; the pin is intentional.
  • Maven Central can answer 429 Too Many Requests during dependency resolution. That is an infrastructure failure: one re-run is justified; a second identical failure needs reporting, not more re-runs.

Dependency-bot PRs

Renovate opens PRs on renovate/* branches; .github/workflows/dependency-auto-merge.yml approves them and merges them once BTrace CI/CD and CodeQL pass.

  • Do not push to renovate/* branches. Renovate force-rebases them, which discards your commits, and any commit you add would be auto-merged under the bot's approval.
  • When a bot PR fails, find the root cause and fix it in a separate PR from develop:
    • an intentional pin or toolchain requirement was bumped → add or tighten a packageRules entry in renovate.json and close the bot PR;
    • the upgrade is wanted but needs code changes → make them in the separate PR, then let Renovate rebase its PR onto the result.
  • Validate renovate.json with npx --package renovate@latest renovate-config-validator --strict renovate.json before pushing a change to it.

Review follow-up

  • Fix small, local asks directly. Anything touching the masked-JAR layout, class-loader boundaries, or the wire protocol is not small: propose the change on the thread and read the architecture docs linked from AGENTS.md first.
  • A behavior change that crosses module or process boundaries needs integration-test coverage (see AGENTS.md); a review asking for it is not optional.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.