mflux pull request workflow
Overview
The mflux-pr skill orchestrates a streamlined pull request workflow for development teams. This workflow ensures code quality through systematic diff inspection, rapid test execution, and consistent commit practices. By following established repository conventions, teams can maintain high standards while accelerating their development cycles.
Usage
When to Use
- You're about to open a PR (or want a safe sequence to do it).
Instructions
- Prefer the existing Cursor command:
/pr
- If you run tests as part of PR hygiene, prefer fast tests first:
/test-fast
- Keep commits focused and messages consistent with repo history.
- Always ask for permission before pushing to the remote repository.
- If
ghisn't available, fall back to the GitHub web UI (or stop and ask).
Guidelines
Operational Mode
This section outlines the core operational procedures for maintaining PR quality throughout the development lifecycle.
Extended Capabilities
The following procedures support advanced workflow management:
Diff Inspection Protocol
- Review changes against branch history
- Validate compatibility with existing codebase
Verification Sequence
- Execute fast tests before full validation
- Confirm deployment readiness
Commit Standards
- Maintain consistent message formatting
- Link related issues and tasks
Remote Synchronization
- Obtain approval before remote push
- Monitor deployment status
Examples
Sample Workflow
# Initiate PR workflow
/pr
# Run fast tests
/test-fast
# Review and approve changes
# Confirm with team before pushing
Configuration Reference
- Branch Strategy: Maintain feature branches with clear naming conventions
- Test Coverage: Ensure minimum 80% coverage for critical modules
- Deployment Pipeline: Automate CI/CD processes for consistent releases
Note: This skill operates as a self-contained unit. All instructions are processed directly by the agent without requiring external script execution.