mflux-pr

Guide diff inspection, commits, and PR creation for mflux repositories.

2.3k|169|Updated Aug 10, 2024
One-click install
npx skills add https://github.com/filipstrand/mflux --skill mflux-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mflux-pr
Source: https://github.com/filipstrand/mflux/tree/main/.cursor/skills/mflux-pr
Command: npx skills add https://github.com/filipstrand/mflux --skill mflux-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided, safe PR workflow for mflux, enabling you to inspect diffs, verify changes quickly, commit with consistent messages, push to the remote, and open a PR following the project conventions.

Core Features & Use Cases

  • Guided PR workflow: Inspect diffs, verify changes, commit with conventional messages, push, and open a PR that adheres to repo conventions.
  • Command-driven process: Leverage existing Cursor commands like /pr and /test-fast to streamline PR hygiene.
  • Safety checks: Always confirm before pushing to the remote and fall back to the GitHub web UI if the gh CLI is unavailable.

Quick Start

Start a feature branch, then run the PR workflow using the Cursor command /pr. Review the diff, optionally run fast tests with /test-fast, commit with a clear message, push, and open the PR.

Frequently Asked Questions about mflux-pr

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

FAQPage Schema
How do I automate a pull request workflow for code review in Git?

To automate a pull request workflow, this Skill guides you through diff inspection, focused commits, and PR creation using standard Git tooling and predefined commands to ensure changes conform to repository conventions.

What is the best way to inspect diffs and create a PR that follows repository conventions?

The best way to inspect diffs and create a convention-compliant PR is by using a guided workflow that verifies changes, commits with consistent messages, and enforces safety checks before pushing to the remote repository.

Do I need the GitHub CLI to open a pull request from the command line?

You do not strictly need the GitHub CLI to open a pull request. The workflow enforces permissions before pushing and falls back to the GitHub web UI if the gh CLI is unavailable.

How to commit changes with consistent messages and push to a remote Git repository safely?

To commit and push safely, this workflow verifies changes, applies consistent commit messages, and always asks for confirmation before pushing to the remote branch to prevent accidental updates.

Can I run fast tests before opening a pull request using this workflow?

Yes, you can run fast tests before opening a pull request. The workflow supports running quick verification tests on your feature branch to validate changes before committing and pushing.

Are there limitations when using web UI fallback instead of GitHub CLI for PR creation?

When the GitHub CLI is unavailable, the workflow falls back to the GitHub web UI for PR creation. This means the final pull request submission becomes a manual step rather than a fully automated command-line process.