From mj-git
This skill should be used when the user asks to create a GitHub Issue, select an issue template, fill issue fields, or start a new task or bug report in MJ System. Triggers on "创建issue", "新建issue", "提issue", "报bug", "新任务", "create issue", "new issue", "report bug", "file issue", "open issue". Uses gh CLI with --body-file and reads .github/ISSUE_TEMPLATE at runtime for title prefix and labels.
npx claudepluginhub mj-agentlab/mj-agentlab-marketplaceThis skill uses the workspace's default tool permissions.
Creates GitHub Issues for MJ System using the project's 5 issue templates. Template-driven: reads `.github/ISSUE_TEMPLATE/<type>.md` at runtime for title prefix and labels, uses `issue-templates-reference.md` for field guidance. Uses `gh` CLI with `--body-file` (same pattern as mj-git-pr).
Creates well-structured GitHub issues using gh CLI with templates for bugs, features, tasks including titles, descriptions, acceptance criteria, and labels. Use for filing bugs or feature requests.
Creates formatted GitHub issues from conversation context with tag selection from git-msg-tags.md, prefixes like [plan][feat], and user confirmation before creation.
Generates GitHub YAML issue templates for bug reports and feature requests in .github/ISSUE_TEMPLATE/. Includes structured fields, auto-labels, and optional config.yml to standardize maintainer info intake.
Share bugs, ideas, or general feedback.
Creates GitHub Issues for MJ System using the project's 5 issue templates. Template-driven: reads .github/ISSUE_TEMPLATE/<type>.md at runtime for title prefix and labels, uses issue-templates-reference.md for field guidance. Uses gh CLI with --body-file (same pattern as mj-git-pr).
Workflow position: optional pre-step before mj-git-branch.
[mj-git-issue] -(optional)-> mj-git-branch -> mj-git-commit -> mj-git-push -> mj-git-pr
Before starting, verify gh is installed and authenticated:
gh auth status
If not installed or not logged in → output install/login guidance and stop (H1).
Ask: "Is this a production emergency bug?"
hotfix. Display reminder: "Hotfix branches are created from main, and the PR target is also main." (H4)| Option | Type | Template | Description |
|---|---|---|---|
| 1 | Feature | feature.md | New feature or requirement change |
| 2 | Bugfix | bugfix.md | Bug report or abnormal behavior |
| 3 | Documentation | documentation.md | Doc creation, update, or restructure |
| 4 | Maintain | maintain.md | CI/CD, Docker, dependencies, tool scripts |
Read the selected template file:
cat .github/ISSUE_TEMPLATE/<type>.md
Extract from the template (single source of truth):
title prefix (e.g. [Feature] ), labels (e.g. feature)**field_name**For field guidance details (fill examples, required vs optional), refer to issue-templates-reference.md.
[Feature] )<prefix><user_input> (e.g. [Feature] Add user authentication module)Fill each field according to the issue type. Per-type field definitions and examples are in issue-templates-reference.md.
Field summary by type:
| Type | Required Fields | Optional Fields |
|---|---|---|
| Feature | what, why, acceptance criteria | notes |
| Bugfix | symptom, reproduction, expected vs actual, environment | — |
| Documentation | change content, change reason, acceptance criteria | — |
| Maintain | change content, impact assessment, acceptance criteria | — |
| Hotfix | symptom, impact scope, reproduction, expected vs actual, environment | — |
Guidance approach:
All issue templates end with a > **... blockquote footer (branch naming guidance for humans). When assembling the Issue body, always strip this footer — do not include it in the final content.
Specifically, remove any trailing lines starting with > that contain branch naming or reference guidance.
Assemble and display the complete Issue for user review:
## Issue Preview
**Title**: [Feature] Add user authentication module
**Labels**: feature
**Body**:
<filled template content without footer>
Use AskUserQuestion to confirm (3 options):
Use AskUserQuestion (3 options):
--assignee @me--assignee <username># Write body to temp file
# Windows: $TEMP/issue-body-<type>.md
# Unix: /tmp/issue-body-<type>.md
# Create Issue
gh issue create \
--title "<title>" \
--body-file <tmp-file> \
--label "<label>" \
[--assignee <user>] # optional
If gh issue create fails → display error message, suggest checking network/permissions (H3).
After successful creation, clean up the temp file.
Display creation result:
## Issue Created
- **URL**: https://github.com/MJ-AgentLab/mj-system/issues/<number>
- **Number**: #<number>
- **Title**: <title>
- **Labels**: <label>
### Next Step (optional)
To start development, use mj-git-branch to create the corresponding branch:
`<type>/<issue-number>-<description>`
The handoff is suggestive, not mandatory — mj-git-branch's issue-id is optional.
| # | Trigger | Skill Behavior |
|---|---|---|
| H1 | gh not installed or not authenticated | Output install/login instructions, stop |
| H2 | User cancels at preview | Clean up temp file, stop |
| H3 | gh issue create fails | Display error, suggest checking network/permissions |
| H4 | User selects Hotfix (Step 1a) | Extra reminder: "Hotfix branch from main, PR target also main" |
| H5 | Issue body contains template footer | Auto-strip > **... blockquote footer, no user prompt |
Complete field-by-field guidance for each issue type with examples in issue-templates-reference.md.