You can enforce rubyfmt locally and in CI by running the same verified formatter check through one pre-commit configuration. The key caveat: the available documentation here does not establish rubyfmt’s current command, supported flags, or an official pre-commit hook ID, so those must be confirmed in the project’s maintained documentation before you add a runnable rubyfmt hook. Don’t copy a guessed hook stanza into your repository.
First verify how rubyfmt should be installed and run
Homebrew Formulae lists brew install rubyfmt for the project fables-tales/rubyfmt; its listing showed version 0.14.1 when checked. Treat that version as a snapshot, not a guarantee of the current release. Check the project’s current documentation for the supported installation method and command before wiring the formatter into automation. Homebrew Formulae: rubyfmt
In particular, establish whether rubyfmt edits files or offers a check-only mode, which flags it supports, and which file extensions it handles. The exact invocation is not established by the available sources, so this article does not invent one. Also avoid confusing rubyfmt with rfmt, a separate Ruby formatter whose instructions may not apply.
Choose a maintained hook or a local hook
Before configuring pre-commit, check rubyfmt’s maintained README or hook definition for the repository URL, immutable revision, hook ID, file filters, and command. These values are specific to the formatter and cannot safely be inferred from a generic pre-commit example.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Maintained remote hook: Use it only if rubyfmt’s project documentation identifies the hook and its supported revision and ID. Pin a release or commit rather than relying on an unverified moving reference.
- Repository-local hook: If the project does not maintain a hook, a
repo: localentry may call the separately installed executable. Confirm the installation prerequisites and exact command first, and ensure its file filters match rubyfmt’s supported inputs.
Once those details are verified, add the hook to .pre-commit-config.yaml, install pre-commit in each developer environment, and run pre-commit install to register the Git hook. See the pre-commit documentation for current CLI and configuration guidance.
Run the same configured check in GitHub Actions
Use the project’s pre-commit configuration as the shared definition of what to check. A local hook helps catch formatting problems before a commit; CI is the enforcement point for contributors who bypass local hooks or use a different environment. Make the CI job fail when the configured check fails.
For Ruby setup, GitHub recommends ruby/setup-ruby; it can select the version specified in a root .ruby-version file. Pin third-party Actions to full commit SHAs, because branch and tag references can move. GitHub Docs: Building and testing Ruby
- Check out the repository with a verified, SHA-pinned checkout action.
- Set up the project’s required Ruby version with a verified, SHA-pinned
ruby/setup-rubyaction. - Install pre-commit and rubyfmt using their documented methods, unless the chosen integration handles the necessary setup.
- Run the configured pre-commit check and allow a nonzero result to fail the job.
This is a sequence, not a ready-to-paste workflow: the verified action SHAs, Ruby version, install commands, and rubyfmt hook details depend on your repository and the current project documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
Choose a CI integration deliberately
The pre-commit/action README provides an integration pattern, but says the action is in maintenance-only mode and generally recommends pre-commit.ci as a faster, more feature-rich option. Treat these as alternatives for running pre-commit—not as rubyfmt-specific endorsements. If you use a GitHub Action, apply GitHub’s SHA-pinning guidance rather than assuming a sample tag is immutable. pre-commit/action README
Decide whether CI checks every file or only changes
For a strong formatting gate, run the configured checks over the full repository in the main CI check. This can catch pre-existing formatting drift as well as problems in a pull request. A changed-files-only run can be faster, but it does not establish that the rest of the repository passes.
pre-commit documents this example for checking a changed range:
pre-commit run --from-ref origin/HEAD --to-ref HEAD
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
Use it only when the workflow has fetched the refs needed for that comparison and when changed-file scope is the intended policy. For caching, pre-commit’s repository store defaults to ~/.cache/pre-commit; it can be redirected with PRE_COMMIT_HOME or XDG_CACHE_HOME. Follow the documentation’s CI caching guidance and key the cache appropriately for the configuration and environment. pre-commit: Advanced features
Quick Recap
Final implementation checklist
- Confirm rubyfmt’s current installation method, release, executable command, flags, file types, and whether it formats in place or supports check-only operation.
- Verify the hook repository, revision, ID, and filters from rubyfmt’s maintained source—or deliberately configure a local hook after confirming its prerequisites.
- Use the same pre-commit configuration locally and in CI.
- Choose full-repository or changed-range scope intentionally, and ensure the CI job fails when its check fails.
- Pin third-party GitHub Actions to full commit SHAs and cache pre-commit only if it benefits repeat runs.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
