Test: Validate create-issue Skill End-to-End Feature Coverage
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
This issue was created to validate the end-to-end feature coverage of the updated create-issue Claude Code skill. It exercises all paths in CREATE mode: template reading, automatic label inference, native type assignment, Technology field mutation via GraphQL, and relationship handling.
The skill being tested is responsible for creating, updating, and querying GitHub issues in this repository, including setting GitHub Project V2 fields and sub-issue relationships.
Acceptance Criteria
- Issue created with correct feature label (
dotCMS : Build) inferred automatically - Native GitHub Issue Type set via REST PATCH (not
gh issue create --type) -
Type : Tasklabel applied - Technology field set to
Platformin Project #7 via GraphQL mutation - Team label (
Team : Enablement) applied without asking the user - Sub-issue relationship can be added via POST to sub_issues endpoint
- QUERY mode returns full state including native type, project fields, and sub-issues
- UPDATE mode validates existing labels as ✓ correct or ✗ gap, not just lists them
Priority
Low
Additional Context
This is a test artifact for skill validation. Safe to close once the skill behavior has been confirmed.
Related skill: ~/.claude/skills/create-issue/SKILL.md
Parent spike: https://github.com/dotCMS/core/issues/34791
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 with ~/.claude/skills/create-issue/SKILL.md and compare CREATE, QUERY, and UPDATE behavior against the acceptance criteria; use parent issue #34791 for context. Verify the stated label, native type, project field, and sub-issue paths through the REST and GraphQL operations. Done when all checklist paths are confirmed and the test artifact can be safely closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, graphql
- Domain
- api, devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100