Write a single-line commit message for Ant Design by reading staged changes, the changes selected for the next commit. It summarizes the full commit intent and follows the style of recent repository commits.
- Write a message for staged changes
- Match the style of recent commits
- Summarize changes across multiple files in one line
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026
Look up Ant Design React components in official documentation to find available settings, default values, and usage examples. Check subcomponents and methods, and consult type definitions in the antd package when TypeScript details are needed.
- Checking component settings and default values
- Finding usage examples and demo code
- Looking up available subcomponents and methods
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026
Prepare Ant Design pull requests from all changes on a branch. It uses official templates, drafts an English title and a Chinese or English body, and asks for approval before creating the pull request.
- Summarize all branch changes for a pull request
- Draft a title and body using an official template
- Check the target branch and change type
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026
Review Ant Design GitHub issues and prepare responses, labels, and closure recommendations. It distinguishes bugs from feature requests, checks bot answers, and presents a complete plan for approval before making changes.
- Draft responses to unanswered issues
- Classify bugs and feature requests
- Review dosubot answers
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026
Update Ant Design projects, mainly from v4 to v5, by reviewing changed component APIs, replacing removed features, and migrating theme settings. The skill also guides use of the official tool for automated code changes.
- Upgrading an Ant Design project from v4 to v5
- Replacing removed components and deprecated properties
- Migrating Less theme settings to theme tokens
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026
Review Ant Design tests to decide whether they should be kept, rewritten, or removed. Examine documented behavior and existing coverage to identify duplicate checks or assertions that merely repeat implementation details, with concise reasons for each conclusion.
- Deciding whether a test should be kept, rewritten, or removed
- Finding assertions that merely repeat implementation details
- Checking for duplicate test coverage
ant-design/ant-design☆ 99.8KUpdated Oct 18, 2026