antd-issue-reply

Automate GitHub issue replies and management for Ant Design projects.

99.0k|54.7k|Updated Apr 24, 2015
One-click install
npx skills add https://github.com/ant-design/ant-design --skill antd-issue-reply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antd-issue-reply
Source: https://github.com/ant-design/ant-design/tree/main/.claude/skills/issue-reply
Command: npx skills add https://github.com/ant-design/ant-design --skill antd-issue-reply

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintainers efficiently manage GitHub issues for the Ant Design project by providing guidelines for replying, classifying, and closing issues, ensuring community engagement and a tidy issue tracker.

Core Features & Use Cases

  • Issue Classification: Differentiates between Bug Reports and Feature Requests.
  • Reply Guidelines: Provides rules for initial replies, handling bot responses, and responding to user feedback.
  • Issue Closure Criteria: Defines when and how to close issues based on inactivity, resolution, or duplication.
  • Language Policy Enforcement: Ensures responses match the language used in the original issue body.
  • Use Case: When a user opens a new issue on Ant Design, this skill can draft a polite, informative reply, categorize the issue correctly, and suggest appropriate labels, all while adhering to the project's communication standards.

Quick Start

Use the antd-issue-reply skill to help draft a response to a new Ant Design GitHub issue.

Frequently Asked Questions about antd-issue-reply

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

FAQPage Schema
How do I automate replying to GitHub issues for Ant Design?

Automating GitHub issue replies for Ant Design involves classifying issues, drafting initial responses, applying labels, and enforcing language policies based on predefined rules to maintain community engagement and a tidy tracker.

What is the best way to manage feature requests and bug reports in GitHub?

Managing feature requests and bug reports requires differentiating between the two, applying appropriate labels, and following specific reply guidelines to ensure clear communication and proper issue closure criteria are met.

When should I close GitHub issues based on inactivity or duplication?

Closing GitHub issues for inactivity or duplication requires evaluating predefined closure criteria, ensuring the issue is resolved, duplicated, or inactive, and applying the correct project communication standards.

How do I ensure GitHub issue replies match the language of the original report?

Matching GitHub issue reply languages requires enforcing a language policy that analyzes the original issue body and automatically drafts responses in the same language used by the reporter.

Can I use predefined rules to apply labels to new GitHub issues automatically?

Applying labels to new GitHub issues with predefined rules is supported by classifying the issue as a bug report or feature request and suggesting appropriate labels according to official project guidelines.