Add skill to add FUS metrics - #8142
Nataliya Valtman (nav-nav) wants to merge 1 commit into
Conversation
Code OwnersPR commands for maintainers
|
|
Hi! It looks like there are no references to any YT issues in the commit messages. |
Egor Andreevich (Egorand)
left a comment
There was a problem hiding this comment.
Overall, the skill worked pretty well except for skipping a couple of steps for unknown reasons. Here are the changes it helped me make:
- #8143
- https://code.jetbrains.team/p/ij/repositories/community/reviews/223231/timeline
- #8153
- https://code.jetbrains.team/p/ij/repositories/community/reviews/223247/timeline
The total spent on adding these two events was 4.31 credits using Claude Sonnet 5.
/final
| the value actually leaves the IDE. This check cannot be automated — hand these | ||
| instructions to the user (or follow them yourself in a sandbox IDE): |
There was a problem hiding this comment.
FWIW, the agent didn't hand me these instructions.
| `kotlin.gradle.performance_v2.<EventName>=…` description in | ||
| `build/events/FUS.properties` ✓. | ||
|
|
||
| ## Commit conventions |
There was a problem hiding this comment.
Not sure why, but the agent did not create a commit, I had to do it myself.
|
|
||
| Note that reporting a value that violates the metric's anonymization policy | ||
| (e.g. a string outside its allowed list) is *not* silently dropped — it | ||
| surfaces as a FUS error, which the integration test below checks for. |
There was a problem hiding this comment.
Suggestion to add a note for the agent to not try to compile the project at this point, as it's unnecessary (or provide clear instructions on how to compile the project). Something along the lines of:
Do not try to compile the code or run tests at this point, as you'll be adding an integration test next.
Adding new fus metrics requires changes in both kotlin and IntelliJ repos. To make this easier, a new skill is introduced