Show HN: Ccv – keep AI-generated files out of your repo
3 comments
Happy to answer questions.
Curious if others are managing AI-generated files differently — especially across multiple projects.
Curious if others are managing AI-generated files differently — especially across multiple projects.
Your project is interesting. But for me, I just let claude code to create gh issues and attach the ai generated files there without flooding into my project repo.
That’s a nice approach.
I tried something similar, but for me the issue was having everything close to the code and easily reusable across projects.
With issues, the context is a bit more "detached", and I found myself not going back to it often.
ccv is more about keeping those files local, quick to access, and still organized without committing them.
But yeah, attaching to issues makes sense too depending on workflow.
I tried something similar, but for me the issue was having everything close to the code and easily reusable across projects.
With issues, the context is a bit more "detached", and I found myself not going back to it often.
ccv is more about keeping those files local, quick to access, and still organized without committing them.
But yeah, attaching to issues makes sense too depending on workflow.
It stores files in a private Git-backed vault and symlinks them into project directories when needed.
So the files are: - accessible locally - version controlled - not part of the public repo
I kept running into the same issue while using AI tools — lots of useful notes and prompts, but no clean way to keep them without polluting repos.
Key features:
- Single private vault (~/.ccv) - Symlink-based linking per project - Automatic .gitignore handling - Works across multiple projects - Optional watch + auto-sync
Blog Post : https://docs.ebuz.xyz/blog/posts/ai-files-messing-up-repos Repo: https://github.com/takielias/claude-code-vault