// Prepare and commit code changes with full verification, pre-commit checks, and tests. Runs verification skill, fixes issues using TDD, executes all test suites, and creates atomic commits. Use when ready to commit changes, before committing, or when asked to prepare a commit.
| name | commit |
| description | Prepare and commit code changes with full verification, pre-commit checks, and tests. Runs verification skill, fixes issues using TDD, executes all test suites, and creates atomic commits. Use when ready to commit changes, before committing, or when asked to prepare a commit. |
Prepare, verify, and commit code changes following project standards.
Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push]
Copy and track progress:
Commit Progress:
- [ ] Step 1: Run verification skill
- [ ] Step 2: Fix issues using TDD
- [ ] Step 3: Run pre-commit checks
- [ ] Step 4: Create atomic commit
- [ ] Step 5: Run ALL test suites (3 REQUIRED):
- [ ] ./gradlew ktlintCheck spotlessApply
- [ ] ./gradlew koverXMLReport
- [ ] ./gradlew verifyPlugin
- [ ] Step 6: Push (optional, ask first)
CRITICAL: Step 5 has THREE mandatory test suites. Skipping any is FORBIDDEN.
Execute the verification skill to analyze code changes:
Verification Progress:
- [ ] Load project rules and standards
- [ ] Trace code paths for modified files
- [ ] Check for semantic changes
- [ ] Identify code smells
- [ ] Run security scans
- [ ] Review PR feedback (if PR exists)
Read and follow: .cursor/skills/verification/SKILL.md
Output: List of issues found, categorized by severity.
For each issue identified by verification:
Before ANY fix:
Never skip TDD. Use implementation skill for complex fixes.
Run:
./gradlew ktlintCheck spotlessApply
./gradlew koverXMLReport
./gradlew verifyPlugin
Get absolute path first:
pwd
Then run:
snyk_sca_scan with absolute project pathsnyk_code_scan with absolute project pathFix any security issues (skip test data false positives).
- [ ] Linting clean (./gradlew ktlintCheck spotlessApply)
- [ ] Security scans clean
- [ ] No implementation plan files staged
- [ ] Documentation updated (if needed)
type(scope): description [XXX-XXXX]
Body explaining what and why.
Types: feat, fix, refactor, test, docs, chore, perf
Extract issue ID from branch:
git branch --show-current
# Review what will be committed
git status
git diff --staged
Never commit:
*_implementation_plan/)git add <files>
git commit -m "$(cat <<'EOF'
type(scope): description [XXX-XXXX]
Body explaining what and why.
EOF
)"
NEVER use --no-verify. NEVER amend commits.
CRITICAL: ALL three test suites MUST be executed after commit but before push. Skipping ANY test suite is FORBIDDEN.
Run these commands IN ORDER and wait for each to complete:
./gradlew ktlintCheck spotlessApply
./gradlew koverXMLReport
./gradlew verifyPlugin
Before proceeding to Step 6, verify:
./gradlew ktlintCheck spotlessApply complete with all tests passing?./gradlew koverXMLReport complete with all tests passing?./gradlew verifyPlugin complete with all tests passing?If ANY answer is "no" or "I didn't run it", STOP and run the missing tests.
If tests fail:
You MUST run each test suite and check it off. Do NOT proceed to push until ALL boxes are checked:
Test Suite Checklist (ALL REQUIRED):
- [ ] ./gradlew ktlintCheck spotlessApply
- [ ] ./gradlew koverXMLReport
- [ ] ./gradlew verifyPlugin
Always ask before pushing.
If approved:
git push --set-upstream origin $(git branch --show-current)
Offer to:
sleep for 60s| Task | Command |
|---|---|
| Format & lint | ./gradlew ktlintCheck spotlessApply |
| Unit tests | ./gradlew test |
| Integration tests | ./gradlew verifyPlugin |
| SCA scan | snyk_sca_scan with absolute path |
| Code scan | snyk_code_scan with absolute path |
| Current branch | git branch --show-current |
| Push | git push --set-upstream origin $(git branch ...) |
Create structured implementation plans for Jira issues using the project template. Use when starting a new task, implementing a feature, when asked to create a plan, or when the implementation skill detects no existing plan.
Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature".
Deep verification of code changes before committing. Traces code paths, detects semantic changes, identifies code smells and security issues. Reads GitHub PR reviews to propose implementation decisions. Use before commits, after implementation, or when asked to verify/review changes.
Deep verification of code changes before committing. Traces code paths, detects semantic changes, identifies code smells and security issues. Reads GitHub PR reviews to propose implementation decisions. Use before commits, after implementation, or when asked to verify/review changes.