agentleFS
yasuflatland-lfyasuflatland-lf/liferay-dummy-factory/.claude/skills/liferay-debug/SKILL.md

liferay-debug

Skill49 starsChanged 38 days agoMITView on GitHub

Investigate a failing build, bundle, integration test, JSONWS/Basic Auth error or Playwright spec in this Liferay workspace. Use when a test fails, the bundle is not Active, the portlet does not render, or a JSONWS call returns 401/403/404 or Guest data.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Reproduce and read the real error: Run the narrowest command (./gradlew :integration-test:integrationTest --tests "<spec>" --info, or the …

    line 8
  2. Very specific:

    Fix the root cause: No fallbacks that hide the failure, no skipped or weakened assertions, no setForce(true), no --no-verify.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Debug a Liferay Dummy Factory failure

  1. Reproduce and read the real error. Run the narrowest command (./gradlew :integration-test:integrationTest --tests "<spec>" --info, or the unit task) and read the first failure, not the last.
  2. Rule out stale state before theorizing. A pass or failure that makes no sense is often a kept container volume or a replayed Gradle result. ./gradlew removeDockerContainer, and for frontend-toolchain changes ./gradlew :modules:liferay-dummy-factory:clean :integration-test:clean, then rerun.
  3. Look up the symptom in docs/guides/troubleshooting.md (bundle, container, JSONWS/auth, Playwright tables). Follow its link to the reference section for the mechanism.
  4. Inspect the live system with the commands at the top of the troubleshooting guide: container log, GoGo shell (lb, diag, headers, scr:info), JSONWS via curl.
  5. Fix the root cause. No fallbacks that hide the failure, no skipped or weakened assertions, no setForce(true), no --no-verify.
  6. Record new knowledge once. A new Liferay behaviour goes into docs/reference/liferay-dxp-api.md or docs/reference/dxp-runtime-config.md, plus one row in the troubleshooting table that links to it. Run node scripts/check-docs.mjs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.