dotCMS / dotCMS/core

[TASK] Document creation of GitHub issue creation skill

Open
#34,460 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dotCMS : CLI Team : Falcon
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Description

This task documents the creation of a new Claude Code skill that streamlines the GitHub issue creation process for the dotCMS repository.

The skill provides:

  • Automatic template discovery and selection
  • Spanish-to-English translation support
  • Smart feature label selection based on content analysis
  • Automatic team and project assignment
  • Structured workflow for consistent issue creation

The skill is located at: .claude/skills/create-issue/

Acceptance Criteria

  • Skill created and functional in .claude/skills/create-issue/
  • Skill reads and uses GitHub issue templates dynamically
  • Skill supports Spanish input with English output
  • Skill automatically applies appropriate labels (Team : Falcon, feature labels)
  • Skill provides clear user feedback with issue URL
  • Skill documented in team knowledge base
  • Team members trained on skill usage

Priority

Medium

Additional Context

This skill improves developer experience by:

  • Reducing time to create well-formed issues
  • Ensuring consistent issue structure and labeling
  • Supporting bilingual team members
  • Automating repetitive template selection and field population

The skill follows the repository's issue template standards defined in .github/ISSUE_TEMPLATE/.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing skill in .claude/skills/create-issue/ and the templates under .github/ISSUE_TEMPLATE/ to understand its workflow. Done means documenting the skill in the team knowledge base and training team members on its usage; the payload does not identify the knowledge-base location or training format.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.