Create, amend, or rename IntelliJ commits with messages that follow the project’s ticket and label formats. Keep each commit focused, explain the reason and decision in the body when needed, and pass the message safely through the shell or PowerShell.
Create, amend, or rename IntelliJ commits and write commit messages.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
SafePush rejects a malformed subject, and each rejection costs a CI round trip.
git status --short and git diff --stat. Read the full diff only for changes you did not make in this session.IDEA-12345 <subject> # a change with a ticket: the id, then one sentence
<label> <subsystem>: <subject> # a change with no ticket
IDEA-12345 the inspection skips a generated file, not
IDEA-12345 fix inspections: generated files. A test, a docs, or a cleanup commit of a ticket takes the same form;
the body says that it is a test or a docs change.tests, cleanup, refactor, docs, format, style, setup, misc.fix(scope): …).IJ-MR-100 in its own last paragraph.In a POSIX shell, use a quoted heredoc:
git commit -F - <<'EOF'
IDEA-12345 concise subject
Why the change was made and what was decided.
EOF
In PowerShell, pass one -m per paragraph, also with --amend. Do not pipe a here-string into -F -.
Windows PowerShell adds a BOM to the subject, and SafePush rejects it.
git commit -m "IDEA-12345 concise subject" -m "Why the change was made and what was decided." -m "IJ-MR-100"
Do not write the message to a file outside the workspace, such as /tmp: that asks for a filesystem approval and leaves a plaintext draft behind. If you need a file, give it a name unique to your session under the gitignored out/, such as out/commit-message-<session>.txt. Several sessions share one working copy, and a peer can overwrite a shared file name between your write and your commit.
MRI-3589 harden single-flight recursion checks
Track active single-flight computations in coroutine context so recursive
awaits fail fast in both the owning coroutine and child coroutines.
IJ-MR-100
IJAI-3334 the published-surface wait of the editor service test names its step and dumps the state
The test failed once on TeamCity with no log line in its 10 s window, and 208 local runs did not reproduce it.
The helper now waits for the subscription and then for the apply, under one deadline, and a failure adds the
state of the test backend and a coroutine dump. No product code changes.
A change with no ticket:
tests cidr: migrate JUnit 5 coverage
Convert remaining JUnit 4 suites under cidr/coverage to JUnit 5.
Parametrized tests now use @MethodSource instead of the Theories runner.
Other cases, such as isolated commits and misc triage: 2_Commits.md. To push, use the safe-push skill.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement or update IntelliJ `AnAction` classes and their `plugin.xml` registrations. Keep labels and descriptions in message bundles, configure optional icons, and launch suspending work through the event coroutine scope so synchronous action handling does not freeze the IDE.
Move IntelliJ JPS test modules to Bazel and diagnose failures that occur only under Bazel. The guide helps trace missing dependencies, plugins, test data, and runfiles, then verify the generated target and migrated tests.
Write or review Kotlin and Java code in line with IntelliJ project conventions. The guidance covers language choice, formatting, sealed types, threading annotations, and safe handling of control flow exceptions so changes fit the surrounding codebase.
Compare how Python type checkers interpret a code snippet or file. The script runs selected tools, including ty, pyrefly, basedpyright, mypy, and zuban, then produces a Markdown report with verdicts, timings, and each checker's diagnostic output.
Shape Compose Desktop UI code by keeping composables focused on rendering and placing application decisions in presenters or coordinators. Get guidance on state ownership, effects, reusable component APIs, lazy-list keys, animation, and performance for individual UI changes.
Audit Compose Desktop code for architecture and runtime issues, including state ownership, effects, coroutine use, lazy lists, animation, and recomposition. It produces prioritized findings with file and line references, while keeping visual design outside the audit scope.