create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels
Profile →npx skills add dyoshikawa/rulesync --skill create-issue --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Create GitHub Issue ## Step 1: Gather Information Receive the issue topic from $ARGUMENTS or the user's description. If the information is insufficient, ask the user to clarify the following: - What needs to be done (the task or problem) - Why it needs to be done (the purpose or motivation) ## Step 2: Research Context Before writing the issue, investigate the relevant parts of the codebase to understand: - Which files and modules are affected - Existing related code patterns - Potential impact and scope of the change ## Step 3: Draft the Issue **Important: All issue content (title, body, labels) must be written in English**, regardless of the language used in the conversation with the user. Create a well-structured issue with the following sections: ```markdown ## Summary A concise one-liner describing what this issue is about. ## Motivation / Purpose Why this change is needed. Explain the problem, user impact, or improvement opportunity. ## Details Detailed description of what needs to be done: - Specific changes required - Files or modules likely affected - Acceptance criteria or expected behavior ## Additional Context Any relevant links, screenshots, or references (if applicab
- Step 1: Gather Information
- Step 2: Research Context
- Step 3: Draft the Issue
- Step 4: Assign Labels
- Step 5: Create the Issue
- Step 6: Report Result
gh label list gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
What does the create-issue skill do?
Create a GitHub issue with detailed description, purpose, and appropriate labels
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill create-issue --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.