[TASK] Document creation of GitHub issue creation skill
Nobody has claimed this yet.
- 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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