dotcms-core

Plugin dotcms-core from marketplace cascade-code-devops-misc-1 in joshuarweaver/cascade-code-devops-misc-1. Commands read from the repo's manifest — 1 month ago.

Skills (29)

• angular-developer

  Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, s

• link-workspace-packages

  Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) lik

• nx-generate

  Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE cal

• nx-plugins

  Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.

• nx-run-tasks

  Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.

• nx-workspace

  Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?',

• dot-cicd-diagnose

  Use when a GitHub Actions workflow fails, PR build breaks, merge queue rejects, nightly reports failures, or user mentions CI/CD test failures in dotCMS/core. Also use for "check build", "diagnose run", "why did CI fail", "flaky test", "merge queue blocked".

• dot-issue-manage

  Create GitHub issues using repository templates. Use when the user asks to create an issue, bug report, feature request, task, spike, epic, or UX requirement. Also use when the user describes a problem, bug, enhancement, or work item that should be tracked. Also use when the user asks to update, que

• dot-pr-spec-summary

  Summarize a spec PR (or any spec document) in simple words — proposed fix, scope, implications, and test coverage — so a reviewer can decide whether to approve without reading the full spec. Use when the user shares a PR URL/number or a spec document and asks to review, summarize, or understand it.

• dot-release-backport-lts

  Backport closed GitHub issues labeled LTS Next Patch to the current LTS release branch. Finds linked PRs, applies diffs, commits, and pushes. Use when applying pending LTS patches to the release branch.

• dot-release-rollback-check

  Check whether a dotCMS release can be safely rolled back to a previous version by inspecting all PRs merged between the two versions for rollback-safety labels. Use when the user asks whether a release or version can be safely rolled back, mentions rollback safety, or runs /check-release-rollback.

• dot-sdk-analytics

  Use this skill when the user asks to install, configure, or set up @dotcms/analytics, sdk-analytics, analytics SDK, add analytics tracking, or mentions installing analytics in Next.js or React projects

• dot-test-plan

  Generates the manual post-merge QA test plan for a merged dotCMS pull request. Reconstructs issue and PR context, consolidates every issue the PR fixed into ONE plan, maps each acceptance criterion to a numbered manual test case (TC-###) with risk, scenario, reproducible steps and an observable expe

• dot-ui-angular-standards

  dotCMS Angular coding standards for the core-web Nx workspace. Use this skill for ANY frontend work under core-web/ — writing or editing a component, service, store, directive, pipe, guard, template, SCSS file, or Jest spec; reviewing a frontend diff; scaffolding new UI; or answering "how do we do X

• dot-ui-vtl-migration

  Migrates VTL (Velocity Template Language) custom field templates from the legacy DotCMS Dojo/Dijit API to the modern DotCustomFieldApi. By default it returns a single inline file ready to paste into the Custom Field: the migrated code inside #if( $structures.isNewEditModeEnabled() ) and the original

• skill-doctor

  Use when a repo skill fails, produces errors, gives wrong instructions, or references stale information. Also use when a command from a skill returns "not found" or "unknown flag", when a skill references a file path that doesn't exist, when a skill's behavior doesn't match the codebase, or to list

• speckit-adr-context

  Consult dotCMS/platform-adrs for Architecture Decision Records relevant to the current feature/fix, so planning treats existing decisions as binding input. Runs as a before_plan hook.

• speckit-analyze

  Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

• speckit-checklist

  Generate a custom checklist for the current feature based on user requirements.

• speckit-clarify

  Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

• speckit-constitution

  Create or update the project constitution from interactive or provided principle inputs.

• speckit-converge

  Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

• speckit-docs-converge

  Extend the convergence gap analysis to documentation drift — docs/, CLAUDE.md, openapi.yaml and REST annotations, spec/plan divergence, and Javadoc. Append-only: findings become tasks in tasks.md, never direct edits. Runs as an after_converge hook.

• speckit-implement

  Execute the implementation plan by processing and executing all tasks defined in tasks.md

• speckit-plan

  Execute the implementation planning workflow using the plan template to generate design artifacts.

• speckit-specify-fix

  Create an issue/bug-resolution specification (defect-framed) from a bug report or issue description. dotCMS variant of /speckit-specify for fixes.

• speckit-specify

  Create or update the feature specification from a natural language feature description.

• speckit-tasks

  Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

• speckit-taskstoissues

  Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

MCP servers (3)

• chrome-devtools

  runs: npx chrome-devtools-mcp@latest

• primeng

  runs: npx -y @primeng/mcp

• angular-cli

  runs: npx @angular/cli mcp

Similar plugins