mflux-release

0
0
Source

Prepare a release in mflux (version bump, changelog, uv lock) without tagging/publishing.

Install

mkdir -p .claude/skills/mflux-release && curl -L -o skill.zip "https://mcp.directory/api/skills/download/4636" && unzip -o skill.zip -d .claude/skills/mflux-release && rm skill.zip

Installs to .claude/skills/mflux-release

About this skill

mflux release prep

Releases are prepared in-repo; tagging/publishing is handled by GitHub Actions.

When to Use

  • You’re preparing a release PR.
  • You need to bump version and update the changelog/lockfile correctly.

Instructions

  • Checklist:
    • Bump version in pyproject.toml
    • Review commits since last release tag:
      • git log --oneline v.<last-version>..HEAD
    • Browse relevant file contents if needed to clarify changes
    • Weigh commit impact: some are minor; skim earlier changelog entries to gauge what's worth reporting vs tiny fixes
    • Add a descriptive entry to CHANGELOG.md based on those commits
    • Always add a ### 👩‍💻 Contributors section to the new changelog entry
    • Source contributor names from merged GitHub PR authors for the changes included in the release, and format them as @handle
    • Prefer one release commit for the release prep work on the branch
    • Name that commit Release <version>
    • Prefer GitHub data over local git author names:
      • Use gh pr list --state merged / related gh queries when available
      • Do not assume gh is installed; if it is unavailable, inspect GitHub on the web instead
      • General pages to check on the web:
        • Closed PRs: https://github.com/<owner>/<repo>/pulls?q=is%3Apr+is%3Aclosed
        • Compare view for release range: https://github.com/<owner>/<repo>/compare/v.<last-version>...HEAD
        • Specific PR page when you know the PR number: https://github.com/<owner>/<repo>/pull/<number>
      • Map included changes to merged PR authors from those pages
    • Do not invent handles, and do not treat local-only commits as contributors unless the user explicitly wants that
    • Update lockfile: uv lock
    • Sanity checks (optional unless requested): make test-fast, make build
    • Manual checks (optional): if the release includes CLI/callback/image-path changes, consider running the mflux-manual-testing skill to exercise the touched commands and visually review outputs.
  • Do not tag releases locally unless explicitly requested (normally handled by CI).

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.