gitcode-issue-gen

Creates GitCode Issues from PR changes or manual descriptions with template selection and bidirectional linking.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill gitcode-issue-gen-wangwindow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcode-issue-gen
Source: https://github.com/WangWindow/CANN-BatchMatMulMaxsum/tree/main/.agents/skills/gitcode-issue-gen
Command: npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill gitcode-issue-gen-wangwindow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually writing GitCode Issues for pull requests is repetitive and error-prone: you must pick the right Issue template, extract technical details from code changes, and keep the PR and Issue cross-referenced. This Skill automates that workflow while enforcing confirmation before any write operation. ## Core Features & Use Cases - PR-to-Issue automation (Path A): Parses a GitCode PR link, clones the repository, inspects the diff, auto-selects an Issue template based on change type (bug-report, feature-request, documentation, RFC), generates the Issue body, and creates bidirectional PR ↔ Issue links via the GitCode API. - Interactive manual drafting (Path B): Collects required fields conversationally, discovers local or remote Issue templates, generates a draft, checks for duplicate Issues, and submits only after user confirmation. - Safety guardrails: Environment pre-checks (token, git, curl), mandatory user confirmation before any write operation, no test Issues against target repositories, and optional self-assignment via the authenticated token user. - Use Case: You merged a documentation PR on GitCode and need a tracking Issue. Provide the PR link, and the Skill selects the documentation template, drafts the body with the PR link appended, and creates the Issue after your approval. ## Quick Start Ask the assistant to create a GitCode Issue for the PR at your GitCode pull request link and confirm the generated draft when prompted.

Frequently Asked Questions about gitcode-issue-gen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitCode Issue from a pull request automatically?

Provide the GitCode PR link and the Skill parses the owner, repo, and PR number, clones the code, inspects the diff, selects an Issue template by change type, and drafts the Issue body. After your confirmation, it creates the Issue via the GitCode API and appends the Issue link to the PR body.

How does the Skill choose which Issue template to use?

Template selection is based on the PR change type: RFC or architecture changes map to request-for-comments, new features or operators to feature-request, bug fixes to bug-report, and documentation changes to documentation. If the recommended template does not exist in the repository, it falls back through requirement, feature-request, then bug-report.

What credentials are required to create Issues on GitCode?

A GitCode API token must be provided through the GITCODE_TOKEN environment variable with permission on the target repository. The token is never printed, logged, or written to files, and all write operations require explicit user confirmation before execution.

Can I draft an Issue without submitting it to GitCode?

Yes. In the manual path you can request a draft only, and the Skill collects required fields, generates the title and body from the discovered template, and shows it for review without calling the create Issue API. Submission happens only after you explicitly confirm.

Does the Skill check for duplicate Issues before submitting?

Yes. Before submission in the manual path, it queries the repository's existing Issues through the read-only GitCode API and shows any potential duplicates with titles and URLs, asking whether you want to continue.

What happens if the GitCode API call fails during Issue creation?

The Skill verifies writes with a follow-up GET request because a 200 response does not guarantee the update persisted. If creation or verification fails, it reports the error and skips optional steps like self-assignment rather than retrying blindly.