alt Hacker NewsI agree that that works pretty well for developers who work with a code repository everyday. But, if you're working on a mono-repo, you can end up with more skills loading than you'd like pretty quickily.
Have you had success with non-technical people using git as their primary sharing source?
Replies
trollbridge • today at 2:24 AM
Git has easy to use GUI tools, particularly if you’re willing to use GitHub. I have not had trouble getting non technical staff to use it (book editors, graphic designers, writers, copywriters)
➕ show 1 reply
est • today at 2:20 AM
yeah skills overwhelming is a problem. Splitting into sub-dirs works for now.
For us it's mostly developers.
➕ show 1 reply
My extension for pi https://github.com/gitsense/pi-brains solves the too many skills problem and it can be adapted to work with any coding agent that supports hooks like Claude and Codex.
You can find a simple example at https://github.com/gitsense/gsc-rules-demos which shows how skills can be injected when needed. The example is:
"read the file at data/accounting/q1.ledger and explain what this ledger tracks"
If you know what the use needs to read or edit, you can inject knowledge/skills for the agent.