You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m considering building a small CLI tool as the first Octacity project.
The idea came from a simple problem: web-based LLMs cannot browse our local workspaces, so sharing a repository often means manually selecting and uploading files.
The tool would package a Git repository while:
respecting .gitignore
excluding .git
including either the committed state or the current working tree
supporting formats such as ZIP and Markdown
The Markdown output could later become more than a source-code dump, with repository structure, language-aware code blocks, symbol indexes, and links between functions and definitions.
The current name ideas are repozip and something broader, since the tool may eventually support more than archive creation.
I’d like to hear thoughts about the idea, possible use cases, and what features it should include.
All contributions are welcome.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Repository packaging tool for Octacity
I’m considering building a small CLI tool as the first Octacity project.
The idea came from a simple problem: web-based LLMs cannot browse our local workspaces, so sharing a repository often means manually selecting and uploading files.
The tool would package a Git repository while:
.gitignore.gitThe Markdown output could later become more than a source-code dump, with repository structure, language-aware code blocks, symbol indexes, and links between functions and definitions.
The current name ideas are
repozipand something broader, since the tool may eventually support more than archive creation.I’d like to hear thoughts about the idea, possible use cases, and what features it should include.
All contributions are welcome.
All reactions