// Create a GitHub issue with detailed description, purpose, and appropriate labels
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Draft a new release of the project.
Dry run for release: summarize changes since last release and suggest version bump.
Scan for malicious code in git diff between a tag/commit and HEAD
| name | create-issue |
| description | Create a GitHub issue with detailed description, purpose, and appropriate labels |
| targets | ["*"] |
Receive the issue topic from $ARGUMENTS or the user's description.
If the information is insufficient, ask the user to clarify the following:
Before writing the issue, investigate the relevant parts of the codebase to understand:
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:
## 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 applicable).
First, get the available labels from the repository:
gh label list
Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the good first issue label if it exists in the repository.
gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
Output the created issue URL and a summary of:
good first issue was applied and why (or why not)