@jahia/agentic 0.4.0 → 0.4.1

package/dist/gemini/.agents/skills/jahia-review-java/references/code-review-output.md

@@ -1,121 +0,0 @@
-# Skill: Code Review Output Format
-
-Load this skill before writing the review output. It defines the section order, finding template, and summary table schema.
-
-## When to load
-
-Always, just before writing the deliverable. Do not load during analysis passes.
-
-## Output mode selection
-
-Detect from context:
-
-| Signal | Mode |
-|---|---|
-| GitHub MCP tools available + a PR number in context | **PR mode**: inline comments + one summary comment |
-| Local filesystem only, module checked out, no PR | **File mode**: single markdown at repo root |
-| A prior `code-review-*.md` exists in the repo | **Follow-up mode**: see `skills/review-followup/SKILL.md` |
-
-When unclear, default to **File mode**.
-
-## File naming (File mode)
-
-`code-review-{module-name}-{YYYY-MM-DD}.md` at the module root. The module name comes from `pom.xml` `<artifactId>`.
-
-If a review already exists for the same date, append `-v2`, `-v3`, etc. Do not overwrite without explicit instruction.
-
-## Section order (mandatory)
-
-```
-# Code review — {module-name} (backend|frontend|fullstack)
-
-- Date: YYYY-MM-DD
-- Scope: {one line — what was reviewed, what was not}
-- Out of scope: {one line — explicit exclusions}
-
-{One short paragraph: overall posture. Lead with what is right; the findings list is for what is wrong. Do not pad.}
-
-## 1. Security
-## 2. API and backend design
-## 3. Bugs and rough edges
-## 4. Documentation and harness drift
-## 5. Build, Maven, and OSGi packaging
-## 6. OSGi and concurrency
-## 7. Tests
-## {N}. Prioritised summary
-## {N+1}. Closing note
-```
-
-Omit sections with no findings — write "No findings." inline only if the absence itself is worth noting (e.g. "No concurrency findings — all `@Component` services are stateless.").
-
-The Closing note is one paragraph. It names the single biggest risk and the single biggest strength. No bullet lists.
-
-## Finding template
-
-Each finding has the same shape:
-
-```markdown
-### {N.M} {Short title} — {severity emoji} P{0|1|2|3}
-
-{One sentence: the problem.}
-
-{2-6 sentences: why it matters, where it manifests, what triggers it. Code snippet if it clarifies in fewer words than prose.}
-
-**Fix:** {Concrete action. Library name + method, or class change, or "accept and document".}
-
-**Effort:** {XS | S | M | L}
-```
-
-Rules:
-
-- **Severity emoji + level** in the heading. Never one without the other.
-- **The problem in one sentence.** If you need a paragraph, you have not understood it yet.
-- **Code snippets are quoted, not paraphrased.** If the bug is in three lines of code, show those three lines.
-- **The Fix line is mandatory.** No exceptions. If there is no fix, the finding is "accept and document" — say so explicitly.
-- **Effort is mandatory.** Authors prioritise by effort × severity. Without effort, the table is half-useless.
-
-## Anchors
-
-Use `ClassName#methodName` as the anchor for code references. Line numbers go stale; method names survive refactors. When a finding spans multiple files, list them under "Affected sites" inline.
-
-## Severity rules
-
-See the parent `AGENTS.md` severity table. One reminder: **the prioritised summary table is your honesty check**. If P0 has more than 5 items, you have inflated severity. Re-evaluate.
-
-## Prioritised summary table
-
-The penultimate section. Schema:
-
-| Priority | Item | Effort |
-|---|---|---|
-| 🔴 P0 | {one-line description with §X.Y backref} | XS/S/M/L |
-| ... |
-
-Sort by priority, then by section number. P3 items can be grouped if numerous.
-
-The backref (`§X.Y`) is mandatory — the reader uses the table as an index into the full findings.
-
-## PR mode specifics
-
-When posting to a PR:
-
-- **Inline comments** for findings that point to a specific file/line span. Use the same finding template, condensed.
-- **One summary comment** at the PR level containing:
-  - The opening paragraph (overall posture).
-  - The prioritised summary table.
-  - Links to the inline comments via their permalinks.
-- **No giant markdown dump in the summary comment.** Inline comments carry the body of each finding.
-
-If a finding cannot be anchored to a line (e.g. "the module has no tests"), it goes only in the summary comment.
-
-## Follow-up mode handoff
-
-If a prior review exists, hand off to `skills/review-followup/SKILL.md`. Do not write a fresh review.
-
-## What not to do
-
-- Do not number findings across the whole document (e.g. "Finding 47"). Number within sections: §1.1, §1.2, §3.1.
-- Do not split a finding into a "problem" finding and a "fix" finding. One finding = one problem + its fix.
-- Do not write a "tl;dr" at the top. The opening paragraph is the tl;dr.
-- Do not include process meta-commentary in the output ("During Pass 2 I noticed..."). The doc is for the author, not a log of your work.
-- Do not write recommendations the author cannot act on alone. If a fix requires a product decision, name the decision; do not pretend it is purely technical.

package/dist/opencode/.agents/skills/jahia/SKILL.md

@@ -1,148 +0,0 @@
----
-name: jahia
-description: Top-level entry point for ALL Jahia tasks. Detects whether the request is about building a module (dev) or managing content (CMS via MCP tools), and delegates to the right skill or combination. Start here if unsure which Jahia skill to use.
----
-
-# Jahia — Universal Entry Point
-
-You are the top-level GPS for all Jahia work. Your job is to understand what the user wants to accomplish, then delegate to the right skill(s) — `/jahia-dev`, `/jahia-content`, or both in sequence.
-
-> **Content operations use MCP tools** via the `jahia` MCP server. Never call Jahia's GraphQL API directly for content creation, querying, or structure discovery — use the MCP tools instead.
-
----
-
-## Step 1 — Classify the request
-
-Read the user's request and classify it using the table below. A task can span multiple categories.
-
-| Category | Keywords / intent | Skill |
-|----------|-------------------|-------|
-| **Module development** | create module, scaffold, content type, CND, view, React, TSX, page template, CSS, build, deploy, compile | `/jahia-dev` |
-| **Personalization / analytics** | jExperience, jCustomer, window.wem, visitor events, Kibana dashboard, personalization, DXP | `/jahia-dev-jexperience` |
-| **Content management** | create content, add article, populate, move, reorganize, publish, query what's in the CMS | `/jahia-content` |
-| **OSGi / back-office** | Java bundle, OSGi service, jcontent action, admin panel, toolbar button, Webpack, Module Federation | `/jahia-dev-osgi-module` or `/jahia-dev-ui-extension` |
-| **E2E testing** | Cypress, test spec, edit mode, component interaction, publish workflow | `/jahia-dev-cypress` |
-| **Java module reference** | OSGi DS, CND definitions, JSP rendering, Drools rules, JCR SQL2, Content Editor JSON, component registry | `/jahia-dev-java` |
-| **API reference** | GraphQL schema, JCR Java/REST API, OAuth/SAML auth, personal tokens, HTML filtering, CSP, security scopes | `/jahia-dev-apis` |
-| **Operations / DevOps** | Docker Compose, Kubernetes, health endpoints, logs, Karaf, provisioning YAML scripts | `/jahia-dev-ops` |
-| **Configuration reference** | jahia.properties keys, cluster setup, operating mode, auth settings, JCR/search tuning | `/jahia-dev-properties` |
-| **Both** | build a component AND fill it with content, design a section AND add pages to it, set up a site end-to-end | Run `/jahia-dev` first, then `/jahia-content` |
-
-If the request is ambiguous, ask one clarifying question:
-> "Are you building or changing **code** (module, views, templates) — or managing **content** (articles, pages, folders) inside a running Jahia site?"
-
----
-
-## Step 2 — Run the right GPS(es)
-
-### Dev only → invoke `/jahia-dev`
-`/jahia-dev` will detect the project state and route to the correct dev sub-skill.
-
-### CMS only → invoke `/jahia-content`
-`/jahia-content` will check the live site and route to the right content management sub-skill.
-
-### Both → run in order
-
-When a task requires code changes **and** content changes, always execute in this order:
-
-```
-1. /jahia-dev                        ← build/update the module code
-2. yarn build && yarn jahia-deploy   ← push the updated module to Jahia (never use yarn dev)
-3. /jahia-content                    ← populate or reorganize content
-```
-
-Rationale: content types must exist in the CMS before you can create nodes of those types.
-
----
-
-## Step 3 — Common compound workflows
-
-Use these recipes as starting points when the task maps to a known pattern.
-
-### "Build a new section on the site"
-```
-1. /jahia-dev-build-component       → define the content type + create the view
-2. /jahia-dev-create-page-template  → (if a new page layout is needed)
-3. /jahia-content-create-content    → create the site if needed, then populate the section with content
-4. /jahia-content-organize          → (if existing content needs to be reorganized)
-```
-
-### "Add an article to the site"
-```
-1. Check the CND — does the article content type exist?
-   → Yes: jump to step 2
-   → No: /jahia-dev-define-content-type + /jahia-dev-create-view first
-2. /jahia-content-create-content    → create the article node + set properties
-3. /jahia-content-publish           → publish it to LIVE
-```
-
-### "Redesign the layout of a page"
-```
-1. /jahia-dev-screenshot       → capture current state for before/after comparison
-2. /jahia-dev-create-view      → update the view / CSS
-3. yarn build && yarn jahia-deploy  → push changes (never use yarn dev)
-4. /jahia-dev-screenshot       → validate the result
-```
-
-### "Set up a new site from scratch"
-```
-1. /jahia-dev-create-template-set   → scaffold the module
-2. /jahia-dev-start-local           → start Jahia locally
-3. /jahia-dev-build-component       → build ONE component at a time (repeat this step per component):
-                                       - invokes /jahia-dev-define-content-type
-                                       - which invokes @jahia-cnd-author (sub-agent, mandatory)
-                                       - then invokes /jahia-dev-create-view
-                                       ⚠ Never batch-write CND — always go through @jahia-cnd-author
-4. /jahia-dev-create-page-template  → create page templates
-5. /jahia-content-create-content    → use `site.templateSets` + `site.create`, then add pages and content
-6. /jahia-content-publish           → publish the site content
-7. /jahia-dev-review                → catch issues before shipping
-```
-
----
-
-## Step 4 — Print the full skill map
-
-Always print this at the end so the user can jump anywhere:
-
-```
-## All Jahia Skills
-
-### 🏗 Development  (/jahia-dev and sub-skills)
-/jahia-dev                       Detect project state, guide to next step ← start here
-/jahia-dev-create-template-set   Scaffold a new JS/React Jahia module
-/jahia-dev-start-local           Start Jahia locally (Docker or bare metal)
-/jahia-dev-build-component       Build a complete component (CND + view) ← shortcut
-/jahia-dev-define-content-type   Define a CND content type + types.ts
-/jahia-dev-create-view           Implement a React view (.server.tsx + CSS Module)
-/jahia-dev-create-page-template  Create a page template with Areas
-/jahia-dev-query-content         Write JCR-SQL2 / useJCRQuery for content listings
-/jahia-dev-review                Code review: 8 critical checks, 9 warnings, 10 suggestions
-/jahia-dev-screenshot            Screenshot reference + local render for visual comparison
-/jahia-dev-debug                 Debug build/deploy/runtime errors end-to-end
-/jahia-dev-cypress               Write Cypress E2E tests for Jahia components
-/jahia-dev-import-from           Implement a component inspired by one on an external URL
-/jahia-dev-jexperience           jExperience + jCustomer: push events, Kibana dashboards, local DXP stack
-
-### ⚙️ OSGi / Back-office extensions
-/jahia-dev-osgi-module           Build or configure an OSGi Java bundle module
-/jahia-dev-ui-extension     Extend jcontent back-office with React 18/Webpack actions or panels
-
-### 📝 Content Management  (/jahia-content and sub-skills)
-/jahia-content                       Detect site state, route to content operations ← start here
-/jahia-content-explore-structure     Map content types, properties, enums & mixins on an unknown site
-/jahia-content-query-content         Query and audit content via MCP tools
-/jahia-content-create-content        Create sites, pages, nodes, folders, and articles
-/jahia-content-media-upload          Upload files and images into Jahia media storage
-/jahia-content-organize              Restructure the tree: move, copy, rename, reorder, delete
-/jahia-content-move-content          Focused move/reorder/delete workflow for an existing branch
-/jahia-content-translate-content     Translate i18n content and page titles
-/jahia-content-publish               Publish, unpublish, and inspect publication status
-### 📚 Knowledge Reference
-/jahia-dev-java              OSGi DS, CND definitions, JSP rendering, Drools rules, Content Editor/jContent UI
-/jahia-jcr-sql2              JCR-SQL2 syntax, filtering, full-text, joins, and pagination guardrails
-/jahia-dev-apis              GraphQL, JCR Java/REST API, OAuth/SAML, personal tokens, HTML filtering, CSP
-/jahia-dev-ops               Docker Compose, Kubernetes, health monitoring, Karaf, provisioning YAML API
-/jahia-dev-properties        jahia.properties and OSGi .cfg configuration keys reference
-```
-

package/dist/opencode/.agents/skills/jahia-content/SKILL.md

@@ -1,157 +0,0 @@
----
-name: jahia-content
-description: Entry point for creating sites, authoring pages, querying content, reorganizing nodes, uploading media, translating, and publishing a Jahia website via MCP tools.
----
-
-# Jahia Content — Content Management GPS
-
-You are the entry point for content work on a live Jahia instance. Understand the request, assess the site state, and route to the right content skill.
-
-> **Never call Jahia's GraphQL API directly for content operations.** Use only MCP tools via the `jahia` MCP server. If a capability is missing, report it — do not work around with curl/GraphQL.
-
----
-
-## Step 1 — Verify the MCP connection
-
-Confirm the `jahia` MCP server is available:
-
-```
-tool: site.list
-```
-
-If this fails, Jahia or the MCP connection is not ready.
-
----
-
-## Step 2 — Detect the site state
-
-Run these checks to understand what exists already:
-
-### A. List available sites
-
-```
-tool: site.list
-```
-
-### B. Discover installed template sets for new site creation
-
-```
-tool: site.templateSets
-args: {}
-```
-
-### C. If a site exists, list its pages
-
-```
-tool: page.list
-args: { "siteKey": "SITE_KEY" }
-```
-
----
-
-## Step 3 — Report the CMS state
-
-Summarize what you found:
-
-```
-🌐 Jahia MCP:       ✅ connected
-📁 Sites:           <site keys>
-🧱 Template sets:   <installed template sets>
-📄 Pages:           <page titles and templates for the chosen site>
-```
-
----
-
-## Step 4 — Route to the right sub-skill
-
-| User intent | Skill |
-|-------------|-------|
-| Explore an unknown site, map areas, inspect types and properties | `/jahia-content-explore-structure` |
-| Create a brand-new site before authoring content | `/jahia-content-create-content` using `site.templateSets` and `site.create` |
-| Create pages, content, or structured trees on an existing site | `/jahia-content-create-content` |
-| Upload files and images to `/sites/<siteKey>/files` | `/jahia-content-media-upload` |
-| Find, inspect, or audit existing content | `/jahia-content-query-content` |
-| Move, copy, rename, reorder, or delete content | `/jahia-content-organize` |
-| Translate content to another locale | `/jahia-content-translate-content` |
-| Publish, unpublish, or check readiness | `/jahia-content-publish` |
-| Do several of the above in sequence | Start with `/jahia-content-explore-structure` if the site is unfamiliar |
-
----
-
-## Direct MCP patterns
-
-### Create a site before authoring pages
-
-```
-tool: site.templateSets
-args: {}
-
-tool: site.create
-args: {
-  "siteKey": "brandSite",
-  "title": "Brand Site",
-  "templateSet": "digitall",
-  "defaultLanguage": "en",
-  "languages": ["en", "fr"],
-  "serverName": "brand.local"
-}
-```
-
-### Publish a page or subtree
-
-```
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["en"]
-}
-```
-
-### Unpublish a page or subtree
-
-```
-tool: publication.unpublish
-args: {
-  "path": "/sites/SITE_KEY/home/about",
-  "languages": ["en"]
-}
-```
-
-### Delete a published node correctly
-
-```
-tool: content.markForDeletion
-args: { "path": "/sites/SITE_KEY/home/old-page" }
-
-tool: publication.publish
-args: {
-  "path": "/sites/SITE_KEY/home/old-page",
-  "languages": ["en"]
-}
-```
-
----
-
-## Full skill map
-
-```
-/jahia-content-explore-structure   Map sites, template sets, pages, areas, and content definitions
-/jahia-content-create-content      Create sites, pages, content nodes, and structured trees
-/jahia-content-media-upload        Upload media and reference it from content
-/jahia-content-query-content       List, inspect, and search content via MCP tools
-/jahia-content-organize            Move, copy, rename, reorder, mark for deletion, and delete content
-/jahia-content-move-content        Focused move/reorder/delete workflow for an existing content tree
-/jahia-content-translate-content   Translate i18n content and page titles
-/jahia-content-publish             Check publication status, publish, unpublish, and handle workflow
-```
-
----
-
-## Critical rules
-
-- Always use MCP tools — never GraphQL directly
-- Use `site.templateSets` and `site.create` when the requested site does not exist yet
-- Always pass `locale` to content creation and update calls
-- Always publish after creating, moving, deleting, or translating content
-- Always explore with `/jahia-content-explore-structure` before authoring on an unfamiliar site
-