Create a Skill for GitHub PR Management Following dotCMS Rules
Open
Nobody has claimed this yet.
stale
Team : Enablement
Type : Task
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Create a new Claude Code skill (dotcms-github-issues companion) for managing pull requests in dotCMS/core, applying the same dotCMS conventions enforced by the issue skill.
The skill should support:
| Mode | Description |
|---|---|
| CREATE | Create a PR from a branch with correct title, body, labels, draft status, and linked issue |
| UPDATE | Update PR title, labels, assignees, reviewers, or convert draft ↔ ready |
| QUERY | Show full PR state: status, labels, reviews, CI checks, linked issues, project fields |
| FIND | List PRs assigned to me, open for my team, or matching a keyword |
dotCMS conventions to enforce
- Branch naming:
issue-{N}-{slug}→ auto-links the issue - Required labels:
Team :,Type :(derived from linked issue template) - Draft by default; promote to ready only when explicitly requested
- PR body populated from
.github/PULL_REQUEST_TEMPLATE.md(if present) - PR linked to Project #7 with Technology field set, matching linked issue
Relationship to dotcms-github-issues
- Shared convention knowledge (team labels, Type labels, Technology mapping) should reference the same authoritative sources (
.github/templates,project-fields.md) - Slash commands:
/create-pr,/update-pr,/query-pr,/find-prs
Acceptance Criteria
- Skill file at
.claude/skills/dotcms-github-issues-prs/(or integrated into existing skill as new modes) -
/create-prcreates a draft PR, applies team + type labels, links the issue, sets Technology in Project #7 -
/query-prreturns title, labels, CI status, review state, linked issues -
/find-prslists open PRs for cached team - Reads PR template from
.github/rather than hardcoding body structure
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 dotcms-github-issues skill, .github/PULL_REQUEST_TEMPLATE.md, and project-fields.md to understand the shared conventions and authoritative sources. Implement the PR skill under .claude/skills/dotcms-github-issues-prs/ or integrate it as new modes, then verify the four slash commands meet the listed acceptance criteria for labels, draft status, issue links, Project #7 fields, and query results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100