rocketmq-rust-pr-submitter

Generate RocketMQ Rust pull request titles and bodies with issue-linked formatting.

1.5k|243|Updated Dec 13, 2023
One-click install
npx skills add https://github.com/mxsm/rocketmq-rust --skill rocketmq-rust-pr-submitter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rocketmq-rust-pr-submitter
Source: https://github.com/mxsm/rocketmq-rust/tree/main/.agents/skills/rocketmq-rust-pr-submitter
Command: npx skills add https://github.com/mxsm/rocketmq-rust --skill rocketmq-rust-pr-submitter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of preparing RocketMQ Rust pull requests by turning issue context, change notes, and validation results into a maintainer-ready PR title and body.

Core Features & Use Cases

  • PR Title Formatting: Generates titles that follow the required issue-linked pattern with the correct emoji for the change type.
  • Template-Aligned PR Bodies: Builds PR descriptions that match the repository's real pull request template and include the correct issue-closing line.
  • Validation and Safety Checks: Helps verify title/body formatting and avoids leaking local machine paths into public PR text.
  • Use Case: A contributor fixing a broker auth bug can quickly produce a ready-to-submit pull request that matches repository conventions and is easier for maintainers to review.

Quick Start

Ask for a ready-to-submit RocketMQ Rust pull request title and body for the linked issue, and include your change summary plus any test results.

Frequently Asked Questions about rocketmq-rust-pr-submitter

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

FAQPage Schema
How do I format a RocketMQ Rust pull request title to pass repository validation?

To format a RocketMQ Rust pull request title, apply the exact [ISSUE #id] pattern and select the correct emoji for your change type, ensuring the title satisfies repository submission conventions and validation checks.

What sections are required in a RocketMQ Rust pull request body?

A RocketMQ Rust pull request body requires template-aligned headings, a summary of changes, test results, and a correctly formatted Fixes line to link and close the associated issue.

How do I link a GitHub issue in a RocketMQ Rust pull request?

You link a GitHub issue in a RocketMQ Rust pull request by including the issue ID in the title's [ISSUE #id] pattern and adding the exact Fixes line in the PR body description.

Can I use this for both bug fixes and documentation updates in RocketMQ Rust?

Yes, you can use this for bug fixes, documentation updates, tests, enhancements, and ready-for-review workflows by applying the correct emoji mapping and PR template for each specific change type.

How do I redact local machine paths from my GitHub PR text?

To redact local machine paths from GitHub PR text, the validation and safety checks identify and remove local file paths from the generated pull request title and body before submission.

Why does my RocketMQ Rust PR fail the validation workflow?

Your RocketMQ Rust PR fails the validation workflow if the title lacks the exact [ISSUE #id] pattern, uses an incorrect emoji mapping, misses the Fixes line, or contains unredacted local machine paths.