Detect and fix AEM Cloud Service code-quality issues locally in Java and Maven projects.
npx skills add https://github.com/aemgdc/aemdev --skill code-assessment-aemgdc
Please help me install this Agent Skill. Skill: code-assessment Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/code-assessment Command: npx skills add https://github.com/aemgdc/aemdev --skill code-assessment-aemgdc
@Inject usage in Sling Models, unbounded queries, missing HTTP timeouts, and legacy listener/scheduler patterns — that cause build failures, OOM outages, and silent runtime bugs. This Skill detects and fixes those issues entirely against the local workspace, with no external services or network calls. ## Core Features & Use Cases - Deterministic local detection: A bundled Java analyzer (scripts/analyze.sh) parses the workspace once and runs per-pattern detectors, emitting structured JSON findings with file, line, and snippet. - Expert pattern skills: Routing to specialized remediation guides covering outdated Maven dependencies, @Inject to injector-specific annotation migration, unbounded query triage, outbound call timeouts, Sling Scheduler, ResourceChangeListener, event migration, replication, and AssetManager modernization. - Surgical, reviewable fixes: Applies minimal edits on a git branch or in place, verifies with mvn compile, never commits or pushes, and enforces one pattern per session with resumable batching for large migrations. - Use Case: Ask it to "scan this AEM project for issues" — it runs every detector, reports findings across all built patterns, then applies a chosen fix (e.g., modernizing Sling Models) after you confirm. ## Quick Start Ask the assistant to scan this AEM project for code-quality issues and report what it finds.High-intent search queries and answers about installing and using this skill.
Ask the skill to scan the repo without naming files; it runs the bundled analyzer in discover mode across all detectors and reports findings with file, line, and snippet. You can also name specific files to assess them directly.
The inject-in-sling-model pattern detects field-level javax.inject.@Inject in @Model classes and replaces each with an injector-specific annotation chosen from the field's declared type, such as @ValueMapValue, @OSGiService, or @SlingObject. Constructor and setter injection trigger a file-level skip.
No, it operates entirely against the local workspace with no external services or network calls. It requires a local JDK 11+ for the analyzer and deliberately avoids Maven Central lookups or mvn versions:display-* commands.
It locates versioned dependencies in pom.xml but never guesses target versions; you must supply the target version before it edits the literal <version> or ${property} entry. Live registry comparison is offered only as a separate step after the report.
No, it never commits, pushes, or opens pull requests. Edits are applied surgically on a git branch or in place, verified with mvn compile, and left for the developer to review and commit.
It performs static detection and remediation only, so issues requiring runtime state, a live AEM instance, telemetry, or history across runs are out of scope. Detection stops with a clear message if no JDK is present, and there is no LLM-scan fallback.
frcusacaInstalls Java 25 and configures a local Maven proxy for Claude Code Web sessions.
ImL1sReview git diffs, fix code issues, run test suites, and generate conventional commits.
adobeCoordinate BPA and CAM data to orchestrate AEM migrations to Cloud Service.
mzffreyvazovAudits Maven dependencies for updates, vulnerabilities, and conflicts via CLI workflows.