liferay/liferay-portal / .claude/skills/pr-check
pr-check
VerifiedCheck that a PR is ready to be sent for review.
validations/workspaces/workspace-compile.md
View on GitHub# Workspace Compile
## Match
`.`
## Command
```bash
cd "${BUILD_ROOT}"
if git ls-files --error-unmatch -- ':(glob)**/src/testIntegration/**' > /dev/null 2>&1
then
./gradlew --continue assemble testIntegrationClasses
else
./gradlew --continue assemble
fi
```
`assemble` compiles every module and builds its jar, runs the JavaScript build, and builds every client extension, which runs `validateClientExtensions` and `validateClientExtensionIds`. `testIntegrationClasses` compiles the integration test sources without running them, so a change that breaks an integration test's call site fails here rather than in CI's `workspaces-integration` batch. Neither pulls in a unit test, an integration test run, or the product bundle.
`testIntegrationClasses` exists only in a workspace with integration test sources. Naming a task that Gradle cannot find fails the whole command before anything compiles, so the command names it only in such a workspace.
`--continue` keeps one broken module from hiding the rest, since Gradle otherwise stops at the first failed task.
Do not add heap flags. A workspace that needs more heap sets `org.gradle.jvmargs` in its own `gradle.properties`, and a flag here would override it.
Report FAIL when a failing task is in something the diff changed, quoting the failing task line and the error. When the failing task is in code the diff did not touch, the workspace is already broken, so report **NOT VERIFIED** for it and name the failing task and the commit that last changed its source. Report **NOT VERIFIED** as well when the run could not proceed, such as a dependency that failed to download.
## Notes
The first run in a workspace resolves the workspace plugin and the product dependencies from the network and is far slower than later runs.
## Time Estimate
~1-3 min warm, longer on the first run in a workspace.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |