feat(dx): replace create-issue skill with dotcms-github-issues#34801
Merged
feat(dx): replace create-issue skill with dotcms-github-issues#34801
Conversation
9 tasks
- post-create: auto-trust mise config (no-op if mise not installed) - post-start: copy frontend caches from base worktree to avoid cold starts - .worktreeinclude: scopes copy to node_modules, Nx, and Angular caches Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces the 232-line CREATE-only `.claude/skills/create-issue/` skill (#34465) with the upgraded `dotcms-github-issues` skill and adds four slash command stubs. New skill capabilities: - CREATE / UPDATE / QUERY / FIND modes - Native GitHub Issue Type set via REST PATCH after creation - Project #7 Technology field set via GraphQL mutation - Sub-issue relationships via REST sub_issues endpoint - Team default caching (~/.config/dotcms/create-issue/default-team) - Cascading team selection (Stage 1 / Stage 2 / free-text) - Type : label derived from template + description keywords - Feature label: no incorrect default; asks when ambiguous - FIND mode: per-team sprint iteration field IDs catalogued in references/project-fields.md; current and previous sprint queries using completedIterations; orderBy UPDATED_AT DESC + states OPEN,CLOSED to avoid 100-item pagination truncation on large issue sets - Three reference files: feature-labels.md, github-apis.md, project-fields.md New slash commands (.claude/commands/): - /create-issue → CREATE mode - /update-issue → UPDATE mode - /query-issue → QUERY mode - /find-issues → FIND mode Closes #34800 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
spbolton
force-pushed
the
issue-34800-dotcms-github-issues-skill
branch
from
c990818 to
7a6c651
Compare
- Fix H1 heading to include FIND mode - Add FE and BE option to Step 5 Technology table - Clarify Step 9 label string: feature label is optional; omit from comma-separated list (not leave a trailing comma) when not selected Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The variable-based mutation pattern (mutation($projId:ID!, ...)) fails
in Claude Code's Bash tool because '!' in 'ID!' gets backslash-escaped
before execution. Replace Section C with the inlined-value pattern
confirmed working during skill validation testing:
mutation { updateProjectV2ItemFieldValue(input:{projectId:"..." ...}) }
Also rename file header from create-issue to dotcms-github-issues.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fmontes
requested changes
Feb 27, 2026
.claude/skills/dotcms-github-issues/references/project-fields.md
Outdated
Show resolved
Hide resolved
… table Remove the hardcoded "Native GitHub Issue Types" table from project-fields.md — the template YAML files already have a `type:` field (bug, task, feature, spike, epic, pillar) that is the authoritative source. Update SKILL.md Step 4b to read the matching .github/ISSUE_TEMPLATE/ file and extract its `type:` value, with an explicit note for ux.yaml which has no type field (use Task). Addresses review feedback from @fmontes on PR #34801. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fmontes
approved these changes
Mar 2, 2026
wezell
approved these changes
Mar 2, 2026
Contributor
wezell
left a comment
wezell
left a comment
There was a problem hiding this comment.
Hope this improves dev experience.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.claude/skills/create-issue/skill with the upgraded multi-modedotcms-github-issuesskill.claude/commands/routing to each modecreate-issueskill directoryWhat's new in the skill
create-issuedotcms-github-issues~/.config/dotcms/create-issue/default-team)dotCMS : Content Managementfeature-labels.mdonlyfeature-labels.md·github-apis.md·project-fields.mdType :labelSprint awareness detail
FIND mode can answer "what is the team working on this sprint?" and "what did the team complete last sprint?" for any sprint-based team. Key implementation details:
ProjectV2IterationFieldID catalogued inreferences/project-fields.mditerations; previous sprint viacompletedIterationson the field — no hardcoded sprint namesorderBy: {field: UPDATED_AT, direction: DESC}+states: [OPEN, CLOSED]to avoid 100-item pagination truncation on teams with 1,000+ issuesSlash commands
/create-issue/update-issue/query-issue/find-issuesTest plan
/create-issue— creates issue with correct labels, native type, and Technology field set in Project testing assign #7/update-issue #N— fetches current state, shows validation table, applies changes/query-issue #N— returns title, labels, native type, project fields, sub-issues/find-issues scout current sprint— returns all in-progress items for Scout/find-issues scout last sprint— returns all Done items from previous sprint without truncation/find-issues enablement— falls back to Status-based results (no sprint field)Closes #34800
🤖 Generated with Claude Code
This PR fixes: #34800