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, query, or view an existing GitHub issue. Also use when the user wants to find, search, list, or discover issues — assigned to them, open for their team, recently active, or matching a keyword. Supports both English and Spanish input.

Jump to install Review files

Repository: dotCMS/core
Last source activity: October 12, 2026 at 13:12
Detected SKILL.md language: English
Stars: 971
Forks: 489

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/dotCMS/core/tree/main/.claude/skills/dot-issue-manage.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/dotCMS/core --skill dot-issue-manage

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

5 files

SKILL.md

Source instructions · Read-only preview

name

dot-issue-manage

description

Back to search Back to installation

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 expected result, and carries the previous plan forward as context. Every case is Manual and starts Not Run Yet: the skill never executes tests, records results, or approves a plan. Runs interactively or fully unattended in CI. Trigger on "post-merge test plan", "QA plan for PR #X", "verify this merged fix", "regression checklist for the merged PR", "what should QA exercise post-merge", "test plan for issue #X", "qa-postfix plan", or when a merged PR labeled "PR : dotbot review" plus "Area : Backend" or "Area : Frontend" triggers the post-merge workflow.

2026-10-03

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 legacy code, untouched, inside #else, with no #parse and no extra files. On request it produces three files instead (_old.vtl, _new.vtl and a #parse router), and it converts existing migrations between the two shapes. Use this skill whenever a user asks to migrate, update, or convert a VTL file, custom field template, or dotCMS field that uses any of: DotCustomFieldApi.get(), DotCustomFieldApi.set(), DotCustomFieldApi.onChangeField(), dojo.ready(), dojo.byId(), dijit.byId(), dijit.form.*, dojoType attributes, or any Dojo/Dijit pattern. Also trigger when the user pastes a VTL snippet and asks "what needs to change" or "can you update this", asks for an inline, single-file or one-file migration ("un solo archivo"),

2026-10-03

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.

2026-10-03

View all from this repository

dot-issue-manage

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository