Skip to content
cccskills
FreePublished on GitHub

flowmark

Fast, consistent Markdown auto-formatter for typographic cleanup, normalization, and clean semantic line breaks. Use when creating, editing, or cleaning Markdown; formatting LLM-generated docs; adopting Flowmark in a repository; adding Markdown format scripts or commit hooks; or replacing Prettier or another Markdown formatter.

The English summary is being prepared. Showing the original description.

jlevy/flowmark83 stars(GitHub 83 + cccskills 0)

Run score Not tested

See how to install

Files included (2)

  • SKILL.md2.5 KB
  • references/project-setup.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- DO NOT EDIT: `flowmark --install-skill` (format=f03 surface=skill-md) -->

Flowmark - Markdown Auto-Formatter

Fast, consistent Markdown auto-formatter. Run it on Markdown you generate or edit so committed diffs stay small and readable. It is conservative and safe to run on every file: it never modifies code blocks or inline code.

Format Markdown

Format in place with all auto-formatting (typography, cleanups, semantic line breaks):

flowmark --auto FILE   # one file
flowmark --auto .      # whole tree (respects .gitignore and .flowmarkignore)

Omit --auto to preview to stdout; pipe stdin with - (e.g. cat FILE | flowmark -).

Use flowmark when it is already on PATH. Otherwise use the fast Rust port with a version-pinned uvx runner (never @latest):

uvx --from flowmark-rs==0.4.0 flowmark --auto FILE

The Python reference remains available when its library API or a newer unported patch is required:

uvx --from flowmark==0.8.0 flowmark --auto FILE

Adopt Flowmark in a Repository

If this skill came from flowmark --skill, run the same runner with --install-skill from the project root to materialize the complete bundle. Then, for a repository-wide migration, Makefile wiring, .flowmarkignore, commit hooks, CI policy, and disabling Prettier or other competing Markdown formatters, read project-setup.md in full before editing.

Full Documentation

Flowmark documents itself. Use the CLI rather than reproducing details here:

  • flowmark --help — every flag: --semantic, --smartquotes, --ellipses, --width, --check, list spacing, and file discovery (--extend-include/--extend-exclude).
  • flowmark --docs — the full guide: configuration, file discovery, editor setup, the Python library API, and installing this skill (flowmark --install-skill).
<!-- This document follows common-doc-guidelines.md. See github.com/jlevy/practical-prose and review guidelines before editing. -->

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

simple-modern-uv

Free

Set up, modernize, or update Python projects using the simple-modern-uv template: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing. Use when starting a new Python project or package; when modernizing, upgrading, or migrating an existing Python package to uv (from Poetry, setuptools, pip, requirements.txt, or PDM); or when updating a project already built from simple-modern-uv to the latest template.

The English summary is being prepared. Showing the original description.

jlevy/flowmark83Updated Sep 5, 2026

tbd

Free

Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, Rust, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, external tracker and Linear integration setup, personal Linear API key onboarding, viewing beads in a live browser, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Rust, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, web, browser, live view, external tracker, Linear, Linear API key, integration setup, checkout library, source code review, or any workflow shortcut.

The English summary is being prepared. Showing the original description.

jlevy/flowmark83Updated Sep 5, 2026

See all skills by jlevy

Report a problem with this skill