yyx990803/yorkie — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2022-07-26
Automatically run linters or tests before every Git commit without remembering to do it manually.
Format code automatically before pushing to a shared repository.
Keep Git hooks working correctly across multiple nested packages in a monorepo.
Replace manual .git/hooks management with a simple package.json configuration.
| yyx990803/yorkie | withkynam/vibecode-pro-max-kit | stephenlthorn/auto-identity-remove | |
|---|---|---|---|
| Stars | 609 | 621 | 576 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | 2022-07-26 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | easy | moderate |
| Complexity | 2/5 | 2/5 | 3/5 |
| Audience | developer | vibe coder | general |
Figures from each repo's GitHub metadata at analysis time.
Yorkie is a tool that makes it easy to set up Git hooks, automated actions that run at specific points in your Git workflow. If you've ever wanted to automatically run tests before you commit code, or format your files before pushing, Git hooks let you do that. Yorkie makes setting them up painless by letting you define them right in your project's package.json file instead of dealing with hidden configuration files. Normally, Git hooks live in a special .git/hooks folder and can be tricky to manage, especially when working on a team. With yorkie, you just add a section called gitHooks to your package.json, list the actions you want to run, and you're done. For example, you might want to run a linter before every commit to catch style issues early, or run tests to make sure nothing breaks. Yorkie automatically sets up Git to call those commands at the right time. This project is specifically designed to solve problems that come up in larger projects where you have multiple packages nested inside each other (a setup called a monorepo). If you have a main project and sub-projects that all use the same Git hooks tool, they can sometimes step on each other and cause confusion. Yorkie fixes this by looking for the package.json file that's closest to your actual Git repository, avoiding those conflicts. It's a small but important improvement for teams managing complex project structures. The README mentions this is a fork of an existing project called Husky, meaning someone took that tool and made improvements specifically to handle these edge cases. You'd use yorkie if you're building a JavaScript project, especially if it's structured as a monorepo with multiple packages, and you want your team to automatically run code quality checks before commits without having to remember to do it manually.
Yorkie lets you set up Git hooks like linting or tests before a commit just by adding a section to your package.json.
Mainly JavaScript. The stack also includes JavaScript, Git.
Dormant — no commits in 2+ years (last push 2022-07-26).
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.