Repository navigation
feat(hooks): refresh the index through husky, and README community conventions - #213
Merged
Merged
Conversation
husky 9 points core.hooksPath at .husky/_, whose shims it regenerates on every install, and husky 8 at .husky itself. `rgr hooks install` refused both as a tracked hooks folder. It now recognizes husky, writes the Ragmir block into the .husky/<hook> scripts husky runs, reports manager=husky, and asks to commit those scripts. Other tracked hooks folders still need --force.
The refusal printed the raw mcpAllowedRoots values, so an umbrella base configured with "." told agents it served "workspaces under .". It now prints the resolved folders the check uses.
…DMEs Compared with eight successful open-source READMEs (Vite, Zod, tRPC, Biome, Orama, Context7, mem0, Chroma), every convention most of them share is now present: the GitHub README shows a three-line quick start in its first lines and a community section, and both READMEs carry downloads and stars badges; the npm README gains the centered logo header.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Upgrading two real projects to Ragmir 6.2 surfaced two library gaps, and the README needed a measured check against successful open-source projects.
core.hooksPath = .husky/_).rgr hooks installrefused it as a tracked hooks folder, andrgr hooks statuscalled the ignored.husky/_shims tracked. husky regenerates those shims on every install; hooks belong in the.husky/<hook>scripts.mcpAllowedRoots: ["."], and the refusal told agents it served "workspaces under .".Changes
git-hooks.ts: husky 9 (.husky/_with itshrunner) and husky 8 (.huskywith_/husky.sh) are recognized; the block goes into.husky/<hook>, reports carrymanager, and the CLI asks to commit the changed scripts. Other tracked folders still need--force.mcp-scope.ts: the refusal names the resolved folders the check uses.Verification