agentleFS
fmindfmind/dotfiles/skills/dprint/SKILL.md

dprint

Skill13 starsChanged 4 days agoMITView on GitHub

Format Markdown, JSON, TOML, and YAML with dprint.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • fmind/dotword for word, first seen Nov 8, 2026

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Put a version-pinned dprint.json (or .config/dprint.json, 0.64+) in the repository root.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

dprint

The formatter for configuration and markup files (JSON, Markdown, TOML, YAML); dprint formats only, while Python formatting and linting live in ruff.

Configuration

Put a version-pinned dprint.json (or .config/dprint.json, 0.64+) in the repository root; never rely on the global fallback config in gates, since it can prompt before fmt.

  1. Copy (default): copy a known-good dprint.json into the project root; it is self-contained and version-pinned. The first run downloads uncached plugins; later runs use dprint's local cache. Bump plugin versions per repository.
  2. Extends (DRY): set "extends" to a single source of truth, a local path or a commit-pinned URL such as "https://raw.githubusercontent.com/fmind/dot/<commit>/dprint.json"; override rules or add plugins locally.

Commands

Repository tasks own the two gate commands; add and pin a plugin with dprint add <plugin>.

[tasks."format:dprint"]
description = "Format JSON, Markdown, TOML, YAML (dprint)"
run = "dprint fmt --allow-no-files" # mise appends the hook's {staged_files}; the flag keeps an empty list from exiting 14

[tasks."check:format"]
description = "Check config and markup formatting (dprint)"
run = "dprint check" # non-zero exit on drift

Gotchas

  • Prefer npm: plugin references: npm:@dprint/markdown@<version> over https://plugins.dprint.dev/...wasm URLs; both resolve, and dprint config update --dry-run previews newer versions, including moving URL plugins to npm specifiers; upgrade-tools applies them.
  • Load plugins for embedded code: the Markdown plugin formats fenced JSON, TOML, and YAML only when those plugins are loaded too.
  • Format staged, check the whole tree: format:dprint takes {staged_files} from the hook, which restages fixes; check:format always runs on the whole tree. Outside a hook, dprint fmt --staged or --dirty selects the staged or uncommitted files itself.

Documentation

  • dprint · Configuration · CLI
  • Releases: dprint
  • Companion skills: mise (task vocabulary), lefthook (the pre-commit hook that calls format:dprint).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.