Skill graphify nel repo
Copia di ~/.claude/skills/graphify (graphifyy 0.9.109) in .claude/skills, accanto a apple-design. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5281c0c62b
commit
c65585043c
10 files changed
+1761
No files matched your search
@@ -0,0 +1,48 @@
|
||||
# graphify reference: commit hook and native CLAUDE.md integration
|
||||
|
||||
Load this when the user asked to install the post-commit hook or wire graphify into a project's CLAUDE.md.
|
||||
|
||||
## For git commit hook
|
||||
|
||||
Install a post-commit hook that auto-rebuilds the graph after every commit. No background process needed - triggers once per commit, works with any editor.
|
||||
|
||||
```bash
|
||||
graphify hook install # install
|
||||
graphify hook uninstall # remove
|
||||
graphify hook status # check
|
||||
```
|
||||
|
||||
After every `git commit`, the hook detects which code files changed (via `git diff HEAD~1`), re-runs AST extraction on those files, and rebuilds `graph.json` and `GRAPH_REPORT.md`. Doc/image changes are ignored by the hook - run `/graphify --update` manually for those.
|
||||
|
||||
If a post-commit hook already exists, graphify appends to it rather than replacing it.
|
||||
|
||||
---
|
||||
|
||||
## For native CLAUDE.md integration
|
||||
|
||||
Run once per project to make graphify always-on in Claude Code sessions:
|
||||
|
||||
```bash
|
||||
graphify claude install
|
||||
```
|
||||
|
||||
This writes a `## graphify` section to the local `CLAUDE.md` that instructs Claude to check the graph before answering codebase questions and rebuild it after code changes. No manual `/graphify` needed in future sessions.
|
||||
|
||||
```bash
|
||||
graphify claude uninstall # remove the section
|
||||
```
|
||||
|
||||
## Source-read freshness
|
||||
|
||||
The source-read guard treats a file newer than `graph.json` as potentially stale,
|
||||
but a checkout can refresh timestamps without changing content. For newer files,
|
||||
the guard checks the exact project-relative path (or an exact legacy absolute
|
||||
path) in the configured output directory's extraction manifest. Every populated
|
||||
AST/semantic hash must match the current content; a matching tier cannot hide a
|
||||
stale tier. Unchanged content retains the normal graph guidance and strict-mode
|
||||
first-read deny.
|
||||
|
||||
Missing, unreadable, malformed or oversized manifests, unknown paths, and absent
|
||||
or invalid hashes retain the conservative stale soft nudge. A `needs_update`
|
||||
marker always softens the guard, even when content matches. Older-mtime files
|
||||
are not hashed; this is a checkout-timestamp check, not a full freshness audit.
|
||||
Reference in new issue
Block a user