一键导入
test
Runs unit tests for hellogsm-server-25 (full suite or specific module/class), summarizes failures with root cause analysis, and optionally reports coverage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Runs unit tests for hellogsm-server-25 (full suite or specific module/class), summarizes failures with root cause analysis, and optionally reports coverage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Git Flow-aware commit skill that auto-detects branch context, separates changes into logical units, and writes messages following project conventions loaded from .agents/skills/commit/references/scope-guide.md
Collect PR review comments, critically assess each one against project conventions, auto-apply valid ones, post refutation replies for invalid ones, and prompt for partial ones. Replaces resolve-pr-comments.
Analyzes commits since branching from develop/main, generates PR title/body following project conventions, and creates the PR via GitHub CLI for hellogsm-server-25.
Checklist-based code review of git diff changes for hellogsm-server-25 (Spring Boot 4 / Java 25). Outputs a ✓/⚠/✗ formatted report covering style, logging, exceptions, API conventions, tests, and security basics.
Guides through DB schema change workflows for hellogsm-server-25 in the correct order (Entity → DTO → Repository → Service → Test) with JPA DDL warnings and 2-phase column deletion strategy.
Scans changed files for hardcoded secrets, SQL injection risks, missing auth/authz, and sensitive data in logs for hellogsm-server-25 (Spring Boot 4 / Java 25).
基于 SOC 职业分类
| name | test |
| description | Runs unit tests for hellogsm-server-25 (full suite or specific module/class), summarizes failures with root cause analysis, and optionally reports coverage. |
You are executing the test skill for hellogsm-server-25.
./gradlew test./gradlew test --tests "team.themoment.hellogsmv3.domain.{domain}.*"./gradlew test --tests "...{ClassName}"./gradlew test
Parse for: total run, failures, skipped, and per-failure: class, method, type, message.
| Failure Pattern | Likely Root Cause |
|---|---|
UnnecessaryStubbingException | Service no longer calls stubbed method |
WantedButNotInvoked | Service behavior changed |
NullPointerException | Missing stub for new service dependency call |
AssertionFailedError: expected X but was Y | Service return value changed |
cannot find symbol | Method renamed/removed in service |
✅ All {N} tests passed ({time}s)
## Test Results
❌ {N} test(s) failed
### Failure 1 — {TestClass} › {DisplayName}
**Type:** {ExceptionType}
**Message:** {message}
**Location:** {file}:{line}
If failures exist:
{N} test(s) failed. Diagnose and fix automatically? (uses test-fixer logic)