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
Other versions1 project uses a version of this.
Word for word · 1
- fmind/dot★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- dot-verifySkill
- acliSkill
- agent-evaluationSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-projectSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- draft-docSkill
- draft-mailSkill
- duckdbSkill
- fmind-visualsSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- git-deliverySkill
- github-actionsSkill
- github-issuesSkill
- github-pull-requestSkill
- github-repositorySkill
- google-developerSkill
- gwsSkill
- hfSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- lesson-learnedSkill
- mcp-setupSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- The first 60 shown.
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
- Very specific: line 19
Put a version-pinned dprint.json (or .config/dprint.json, 0.64+) in the repository root.
≈ “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.
Files
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.
- Copy (default): copy a known-good
dprint.jsoninto 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. - 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 driftGotchas
- Prefer
npm:plugin references:npm:@dprint/markdown@<version>overhttps://plugins.dprint.dev/...wasmURLs; both resolve, anddprint config update --dry-runpreviews 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:dprinttakes{staged_files}from the hook, which restages fixes;check:formatalways runs on the whole tree. Outside a hook,dprint fmt --stagedor--dirtyselects 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).
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
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.

