skills.rest
dotCMS
dotCMSOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dot-issue-manage

Create, update, query, and find GitHub issues in dotCMS/core using repository templates and project fields.

950|482|Updated Mar 15, 2012
Search Tags:#gh CLI#dotcms#graphqL#gitHub issues#Sprint Planning#Project management#Issue tracking
One-click install
npx skills add https://github.com/dotCMS/core --skill dot-issue-manage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dot-issue-manage
Source: https://github.com/dotCMS/core/tree/main/.claude/skills/dot-issue-manage
Command: npx skills add https://github.com/dotCMS/core --skill dot-issue-manage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually creating well-formed GitHub issues in dotCMS/core requires knowing the right template, labels, team assignment, native issue type, and Project #7 field values. This Skill automates that entire workflow and also lets you update, query, and discover existing issues without memorizing gh CLI commands or GraphQL mutations.

Core Features & Use Cases

  • Template-driven issue creation: Classifies your request as Defect, Task, Spike, Feature, Epic, or UX, reads the matching template from .github/ISSUE_TEMPLATE/, and builds a structured body with refined acceptance criteria.
  • Full lifecycle management: Update labels, titles, native GitHub issue types, project Status/Technology/Priority fields, and sub-issue relationships on existing issues.
  • Issue discovery (FIND mode): List issues assigned to you, open for your team, filtered by sprint (current/next/previous), recently updated, or matching a keyword, with stale-work flags and board links.
  • Use Case: Say "create a defect for the content search leaking info with limited users" and the Skill classifies the type, runs an ambiguity-resolution loop to write testable acceptance criteria, applies the correct Team/Type/feature labels, sets the native issue type, and assigns the Technology field in Project #7.

Quick Start

Ask the assistant to create a GitHub issue describing your bug or task in plain language, for example: create a defect issue for the login page throwing a 500 error after save.

Frequently Asked Questions about dot-issue-manage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub issue from a template using the gh CLI?▼

Classify the request type (Defect, Task, Spike, Feature, Epic, or UX), read the matching template from .github/ISSUE_TEMPLATE/, then run gh issue create with --title, --body, and --label flags. Do not use the --template flag because it is incompatible with --title and --body in non-interactive mode.

How do I set the native GitHub issue type after creating an issue?▼

Use a REST PATCH call: gh api repos/dotCMS/core/issues/ISSUE_NUM -X PATCH -f type='Bug'. The gh issue create command has no --type flag, so this PATCH is mandatory right after creation. Valid types include Bug, Task, Spike, Feature, Epic, and Pillar.

How do I find my team's issues for the current sprint on GitHub?▼

Use a GraphQL query against the team's iteration field (e.g., Scout Sprint) in Project #7, filtering issues by the sprint title whose startDate covers today. Do not use gh issue list for sprint queries because it returns the oldest 100 issues and misses recent Done items.

Can I add a sub-issue to an existing GitHub issue?▼

Yes. Get the child issue's integer database ID with gh api repos/dotCMS/core/issues/CHILD_NUM --jq '.id', then POST it to the parent's sub_issues endpoint with -F sub_issue_id=CHILD_DB_ID. The endpoint requires the database ID, not the display number.

Why do GitHub project field mutations fail with the gh CLI?▼

Project field mutations fail when the GitHub CLI token lacks project scopes. Refresh authentication with gh auth refresh -s read:project -s project --hostname github.com, then retry the GraphQL updateProjectV2ItemFieldValue mutation.

How do I skip the acceptance criteria clarification step when drafting an issue?▼

Include a quick-draft trigger phrase such as "quick draft", "rápido", or "skip ambiguities" in your request. The Skill then skips the Issue Refinement loop and writes a short placeholder acceptance criteria section instead.

Related Skills

Explore More Software Engineering Skills→
EpiphyticEpiphytic
7

ticket-triage

Categorize support tickets and assign P1-P4 severity levels.

Official
Advanced
fiberplanefiberplane
78

fp-review

Automates code review workflows linking commits to issues and stories.

Official
Advanced
interactive-incinteractive-inc
1

issue

Automate GitHub issue creation, updates, and pull request linkage.

Official
Intermediate
equaltoaiequaltoai
3

create-github-project

Convert approved roadmaps into GitHub Projects v2 with milestones and issues.

Official
Intermediate