You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 58f0ede
Browse filesBrowse the repository at this point in the historyBrowse files
docs(agents): Remove duplicated build commands and rules (#5971)
* docs(agents): Remove duplicated build commands and rules
AGENTS.md is force-read at the start of every session, so anything stated
there costs context on every task. Several rules had accumulated multiple
copies of themselves within that one file.
`spotlessApply`/`apiDump` was stated five times in AGENTS.md; it is now
stated once as a command and once as a workflow step, with the underlying
facts (Spotless enforces formatting, `.api` files are generated) kept where
they belong. The Testing command block is dropped in favour of the `test`
skill, which already resolves the per-module task and the unit-vs-system
split and does not drift. The Repository Skills bullet list restated skill
descriptions that the harness already injects, so it is now a pointer.
In the rules, `new_module.mdc`'s "Important Notes" was a verbatim
restatement of the AGENTS.md contributing guidelines, and `api.mdc` repeated
the opt-in-by-default rule in passing; both now defer to their canonical
homes.
No guidance is lost — every removed line is still stated somewhere that is
loaded when it applies.
* docs(agents): Refresh new_module rule and cover full system-test runs
Validating the previous commit with agents surfaced two gaps.
`new_module.mdc` had drifted from the repo. Its README badge snippet still
used the retired maven-badges.herokuapp.com format, while every current row
in README.md uses shields.io with a central.sonatype.com link. It also never
mentioned four steps that every existing integration module performs: the
`SENTRY_*_SDK_NAME` constant in `Config.kt` consumed by buildConfig and the
jar manifest, the `libs.versions.toml` entry paired with a `compileOnly`
dependency, self-registration via `SentryIntegrationPackageStorage.addPackage`
and `addIntegrationToSdkVersion`, and the integrations dropdown in the issue
template. It now also points at `sentry-kafka` and `sentry-android-timber` as
build-script templates, and records that `sentry-bom` and the root build file
need no change because they iterate over subprojects.
The `test` skill only ever ran a single module, so folding the AGENTS.md
testing block into it dropped the only reference to running the whole system
test suite. Step 3b now covers `make systemTest` and `make systemTestInteractive`.
Copy file name to clipboardExpand all lines: .claude/skills/test/SKILL.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,6 +78,14 @@ test -d .venv || make setupPython
78
78
79
79
This starts the mock Sentry server, starts the sample app (Spring Boot/Tomcat/CLI), runs tests via `./gradlew :sentry-samples:<sample-module>:systemTest`, and cleans up afterwards.
80
80
81
+
To run **every** system test instead of one module, use the Makefile targets — they also create the
82
+
venv for you:
83
+
84
+
```bash
85
+
make systemTest # all system tests (--all)
86
+
make systemTestInteractive # pick the setups to run (--interactive)
0 commit comments