Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
Use treefmt when an agent needs one repo-level formatting plan across multiple languages instead of stitching formatter commands together ad hoc.
--- name: run-one-formatter-plan-across-a-mixed-language-repo-c12b114209a2 slug: "run-one-formatter-plan-across-a-mixed-language-repo-and-keep-generated-edits-predictable-with-treefmt" description: "Use treefmt when an agent needs one repo-level formatting plan across multiple languages instead of stitching formatter commands together ad hoc." github_stars: 977 verification: "security_reviewed" source: "https://github.com/numtide/treefmt" author: "Numtide" publisher_type: "company" category: "Code Quality & Review" framework: "Multi-Framework" tool_ecosystem: github_repo: "numtide/treefmt" github_stars: 977 npm_package: "treefmt" npm_weekly_downloads: 18627 --- # Run one formatter plan across a mixed-language repo and keep generated edits predictable with treefmt Use treefmt when an agent needs one repo-level formatting plan across multiple languages instead of stitching formatter commands together ad hoc. ## Prerequisites treefmt, the underlying language formatters you plan to invoke, a repository-level treefmt configuration file, and shell access. ## Installation Basic usage or getting-started notes: - What if that single command would handle all the formatters in parallel? And only format files that have changed since the previous run? - When formatters are run in a script, they process all the files they encounter, regardless of whether or not - You can install treefmt by downloading the binary. Find the binaries for different architectures [here](https://github.com/numtide/treefmt/releases). - Source: https://github.com/numtide/treefmt - Extracted from upstream docs: https://raw.githubusercontent.com/numtide/treefmt/HEAD/README.md ## Documentation - https://treefmt.com/latest/ ## Source - [Agent Skill Exchange](https://agentskillexchange.com/skills/run-one-formatter-plan-across-a-mixed-language-repo-and-keep-generated-edits-predictable-with-treefmt/)--- name: run-one-formatter-plan-across-a-mixed-language-repo-c12b114209a2 slug: "run-one-formatter-plan-across-a-mixed-language-repo-and-keep-generated-edits-predictable-with-treefmt" description: "Use treefmt when an agent needs one repo-level formatting plan across multiple languages instead of stitching formatter commands together ad hoc." github_stars: 977 verification: "security_reviewed" source: "https://github.com/numtide/treefmt" author: "Numtide" publisher_type: "company" category: "Code Quality & Review" framework: "Multi-Framework" tool_ecosystem: github_repo: "numtide/treefmt" github_stars: 977 npm_package: "treefmt" npm_weekly_downloads: 18627 --- # Run one formatter plan across a mixed-language repo and keep generated edits predictable with treefmt Use treefmt when an agent needs one repo-level formatting plan across multiple languages instead of stitching formatter commands together ad hoc. ## Prerequisites treefmt, the underlying language formatters you plan to invoke, a repository-level treefmt configuration file, and shell access. ## Installation Basic usage or getting-started notes: - What if that single command would handle all the formatters in parallel? And only format files that have changed since the previous run? - When formatters are run in a script, they process all the files they encounter, regardless of whether or not - You can install treefmt by downloading the binary. Find the binaries for different architectures [here](https://github.com/numtide/treefmt/releases). - Source: https://github.com/numtide/treefmt - Extracted from upstream docs: https://raw.githubusercontent.com/numtide/treefmt/HEAD/README.md ## Documentation - https://treefmt.com/latest/ ## Source - [Agent Skill Exchange](https://agentskillexchange.com/skills/run-one-formatter-plan-across-a-mixed-language-repo-and-keep-generated-edits-predictable-with-treefmt/)
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.