← all publishers

maxence2997

@maxence2997 source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 20 hours ago last updated

1. ▌
   Mx Pr · maxence2997 bundle

   Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name]
   0
   installs
2. ▌
   Mx Flow · maxence2997 bundle

   Full development workflow orchestrator: brainstorm → plan → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a feature or significant change from scratch. Usage: /mx-flow <topic>; /mx-flow status [name]; /mx-flow finish <name>.
   0
   installs
3. ▌
   Mx Commit · maxence2997 bundle

   Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto]
   0
   installs
4. ▌
   Mx Doctrine · maxence2997 bundle

   Shared execution doctrine for all mx-* skills: model dispatch and escalation, delegation templates, judgment rubrics (when done / when to ask / wrong-direction signals), verification contracts, maintenance protocol. Consult when dispatching sub-agents, when repeatedly failing, or before editing any mx-harness file. Usage: /mx-doctrine [topic]
   0
   installs
5. ▌
   Mx Brainstorm · maxence2997 bundle

   Turn a rough idea into an approved design spec: clarifying questions in one batch, 2-3 distinct approaches with trade-offs, spec (and ADR when a real choice was made) written to ~/.mx/<project>/<name>/. Hard gate: no implementation until the user approves the spec. Use when starting any feature or non-trivial fix.
   0
   installs
6. ▌
   Mx Team Review · maxence2997 bundle

   Deep code review of a local git diff or files against this user's own engineering standards (Go, C#), written to a report file that /mx-review-triage consumes. Use before commit/merge when you want the standards-based review, not a quick diff scan. Usage: /mx-team-review [diff-spec] | --repo <path>
   0
   installs
7. ▌
   Mx Review Triage · maxence2997 bundle

   Triage review findings — from local mx-team-review reports or GitHub/GitLab PR comments — into fix / track / skip buckets by validity, severity (P0-P3), and cost, then execute approved decisions. Use after mx-team-review or when handling PR feedback before merge. Usage: /mx-review-triage [--source review | --source pr <id|url>]
   0
   installs