skills.rest
Ascend
AscendOFFICIAL
Explore all skills by this author →
WebsiteGitHub

mindie-sd-community-governance

Enforces MindIE-SD documentation, commit, PR, and governance conventions with fixed review steps.

14|5|Updated Mar 30, 2026
Search Tags:#code review#pull request#governance#sphinx#bilingual docs#commit convention#mindie-sd
One-click install
npx skills add https://github.com/Ascend/MindIE-SD --skill mindie-sd-community-governance-ascend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mindie-sd-community-governance
Source: https://github.com/Ascend/MindIE-SD/tree/main/.agents/skills/mindie-sd-community-governance
Command: npx skills add https://github.com/Ascend/MindIE-SD --skill mindie-sd-community-governance-ascend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Contributors to the MindIE-SD repository often produce inconsistent commit messages, PR descriptions, bilingual documentation, and governance changes because the rules are scattered across AGENTS.md, templates, and config files. This Skill centralizes those conventions into fixed review steps with minimal context reading and deterministic output. ## Core Features & Use Cases - Commit and PR conventions: Generates ready-to-use commit titles in [Type][Scope]Summary format, PR titles, and PR body drafts covering the four required template sections (Which issue(s), Purpose, Test Plan, Test Report). - Bilingual documentation checks: Verifies Chinese/English page pairing under docs/zh/ and docs/en/, checks {toctree} navigation in both index.md files, and provides Sphinx build verification commands. - Governance and release policy updates: Handles changes to contributor workflows, PR/Issue templates, version sources (version.py, pyproject.toml), and release notes with a fixed six-item output template. - Use Case: A contributor asks how to title a commit fixing a pattern bug; the Skill returns a compliant title like [Bugfix][pattern] Fix RMSNorm matching for get_attr inputs plus a PR title and body draft. ## Quick Start Ask the assistant to review your MindIE-SD documentation change or draft a compliant commit message and PR description for your current changes.

Frequently Asked Questions about mindie-sd-community-governance

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

FAQPage Schema
How do I write a commit message for the MindIE-SD repository?▼

Use the [Type][Scope]Summary format where Type is one of Feature, Bugfix, Docs, CI, Refactor, Test, or Chore, and Scope is a short English module name. For example: [Bugfix][pattern] Fix RMSNorm matching for get_attr inputs. Avoid vague words like update or fix issue.

What sections must a MindIE-SD pull request body contain?▼

The PR body must follow .gitcode/PULL_REQUEST_TEMPLATE.md and cover four blocks: Which issue(s) this PR fixes, Purpose, Test Plan, and Test Report. Use Fixes # for full resolution and Fix part of # for partial resolution, keeping placeholders when information is missing.

How do I keep Chinese and English documentation in sync?▼

When editing docs/zh/ pages, check for a matching docs/en/ page and vice versa; the verified baseline shows one-to-one pairing except zh/appendix/error_code.md and log.md. For homepage or navigation changes, check the {toctree} blocks in docs/zh/index.md and docs/en/index.md.

How do I verify Sphinx documentation builds after editing docs?▼

Install dependencies with python -m pip install -r docs/requirements-docs.txt, then run python -m sphinx -b html docs docs/_build/html. If the build was not actually executed, the output must state that only suggested verification commands were provided.

When should the mr_ruleset xlsx asset be consulted?▼

Read assets/mr_ruleset_20260327101328.xlsx only when the task involves code, scripts, static checks, or MR quality gates. It provides static code rules, not commit or PR title templates, so extract only rules relevant to the current language or change type.

What tasks are outside the scope of this governance skill?▼

It does not cover general engineering implementation or the repository default workflow, which is defined by AGENTS.md. Python formatting belongs to the code-standards skill and Markdown formatting to the markdown-lint skill.

Related Skills

Explore More Software Engineering Skills→
AscendAscend
31

ascend-inference-repos-copilot

Answer questions about Ascend inference repositories with cited code references.

Official
Advanced
dimakisdimakis

land-pr

Shepherd GitHub pull requests through CI checks, reviews, and squash merges.

Community
Intermediate
radius-projectradius-project
1.7k

radius-markdown-lint

Lint and fix Markdown files using markdownlint-cli2 and markdown-table-formatter.

Official
Intermediate
fartmonarchfartmonarch
1

chinese-commit-conventions

Standardize Chinese Git commit messages and changelog configuration.

Community
Intermediate