Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, lean overview with strong workflow checkpoints and clean one-level reference disclosure. Its only gap is actionability: the body directs to references instead of showing executable migration code.
Suggestions
Include a minimal copy-paste @ChangeUnit example (with @Execution and a rollback hook) directly in the body so the core task is actionable without opening references.
Show a short quarkus.mongock.* / application.properties snippet for migrate-at-start so basic configuration is executable inline.
Add a one-line note on how to verify migrations ran (e.g., checking the mongockLock/changeLog collection) to strengthen the verification step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude's competence, and avoids explaining basic Quarkus/MongoDB concepts; every section earns its place. | 3 / 3 |
Actionability | It gives concrete build commands ('./mvnw compile', 'mvn clean verify') but the migration guidance itself is mostly directive pointers to references rather than executable @ChangeUnit code in the body. | 2 / 3 |
Workflow Clarity | A clear four-step workflow with explicit MANDATORY/SAFETY/VERIFY checkpoints provides feedback loops for the risky compile-then-migrate-then-verify sequence. | 3 / 3 |
Progressive Disclosure | The body is a concise overview with three well-signaled, one-level-deep references (all confirmed to exist), with no nested pointer chains. | 3 / 3 |
Total | 11 / 12 Passed |