Menu
Allows to prepares the current branch for a pull request. Use when ready to create a PR or before committing changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Allows to create new AI agents following the project's architecture patterns.
Allows to review an open GitHub PR for the current branch, applying project-specific and Java best practice criteria, and adds inline comments directly to the PR.
Allows to create new unit tests following established patterns and conventions.
Allows to commit all files and push them to the remote repository.
Allows to plan and guide the implementation of new features or modification of existing features, ensuring best practices, modern design patterns, and proper planning. Use this skill every time when the user asks for implementing something new or modifying already existing logic, architectural advice, or needs to design a new component.
Allows to execute unit tests and systematically resolve all test failures.
| name | prepare-pr |
| description | Allows to prepares the current branch for a pull request. Use when ready to create a PR or before committing changes. |
// turbo-all
This skill provides a comprehensive workflow to prepare your Java code for a pull request. It runs all CI checks locally, fixes any issues, and creates a well-documented pull request.
Proceed autonomously when steps complete successfully. STOP and ASK the user only for: blockers/unfixable errors, ambiguous decisions, or approval before committing. Do NOT ask for confirmation on routine passing steps.
Java 25 (Temurin recommended) | Maven 3.9+ | gh (GitHub CLI)mvn clean install -DskipTests # Initial build
mvn clean install -DskipTests -e # If build fails, run with full output
If compilation errors occur, STOP, present errors to user, apply fixes per user guidance, and re-run until build succeeds.
mvn test # Run all tests with coverage
mvn test -pl <module_name> # Test specific module (e.g., agent_core, ui_test_execution_agent)
If tests fail, STOP and present failure details. Analyze causes (code bug vs. outdated test), ASK user which approach to take, apply fixes, and re-run until all tests pass.
mvn license:check # Verify license headers
mvn license:format # Auto-fix missing headers (if issues found)
git fetch origin main
git diff origin/main...HEAD
Review the diff and categorize changes according to the structure in resources/pr_body_template.md (Features, Bug Fixes, Refactoring,
Tests, Documentation, Dependencies, Configuration). This analysis will be used for README updates and PR description.
Review and update README.md to reflect current code state:
Check if changes affect any skills in .agent/skills/:
Get-ChildItem -Path ".agent/skills" -Directory | Select-Object Name
Update SKILL.md, resources, scripts, or examples if workflow steps, templates, or patterns changed. Explicitly note if no skill updates are needed.
git status # Summary of changed files
git diff # Detailed diff
git diff --cached # Diff of staged files
Present summary of all changes made, then proceed to commit:
git add -A
git commit -m "<type>: <description>"
git push -u origin HEAD
Commit/PR Naming Conventions (conventional commit style):
| Prefix | Use Case |
|---|---|
feat: | New features |
fix: | Bug fixes |
refactor: | Code improvements |
chore: | Maintenance, license fixes, dependency updates |
docs: | Documentation updates |
gh pr create --title "<type>: <short summary>" --body "<description>"
Use the change analysis from Step 4 and the template structure from resources/pr_body_template.md for the PR body.
| Issue | Solution |
|---|---|
| Compilation errors | Check missing imports, incompatible types; use -P windows or -P linux for OS-specific builds |
| Test failures | Verify mock initialization (MockitoAnnotations.openMocks(this)), check test resources in src/test/resources |
| License issues | Run mvn license:format; check template config in pom.xml |
| PR creation fails | Run gh auth login; ensure branch is pushed first; rebase if behind main |
Before creating the PR:
mvn clean install -DskipTests)mvn test)SafeToAutoRun to true for all build, test, and git commands mentioned in this skill.>) to capture command output. Instead, rely on the agent's built-in command output capturing.