summaryrefslogtreecommitdiff
path: root/Brewfile
diff options
context:
space:
mode:
authorIgor Soarez <igor@soarez.org>2026-09-22 11:21:40 +0300
committerIgor Soarez <igor@soarez.org>2026-09-22 11:21:40 +0300
commitb9e58b099d2c9fca930f94f54fbfef0675a17974 (patch)
tree34bd9719a1a8fd9ba5c809bfae28ce137a467dca /Brewfile
parentf31a7a6d69713d45463d53765c9e39aa06290f8c (diff)
tree-sitter-cli, and: a read-only clone hands back a change request
An https clone of this repo cannot push -- the host serves it anonymously and refuses the push with a 403 -- and that is how a machine whose owner cannot hold a key gets it. An agent troubleshooting there would edit a tracked file, see the fix applied, and lose it at the next pull, or leave that clone unable to fast-forward and quietly cut off from changes. CLAUDE.md now says how to tell the two cases apart, and what to do instead: make it machine-local where a hook covers it, or hand back a change request -- paths, the actual diff, why, and how to verify -- stating that nothing was applied. AGENTS.md is a symlink to CLAUDE.md, so the agents that look for that name get the same file rather than a second copy to drift. tree-sitter-cli: nvim-treesitter generates and compiles its parsers with it.
Diffstat (limited to 'Brewfile')
-rw-r--r--Brewfile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Brewfile b/Brewfile
index 0a7dfa3..6fc63ca 100644
--- a/Brewfile
+++ b/Brewfile
@@ -29,6 +29,7 @@ brew "fswatch" # bin/sz-wait-for
brew "n" # node versions, under $N_PREFIX
brew "bash-completion"
brew "shellcheck"
+brew "tree-sitter-cli" # nvim-treesitter generates and compiles parsers with it
cask "alacritty"
cask "hammerspoon"