TeamContext – Git-native shared context for vibe coding teams
Git-versioned team context for Claude Code teams; reviewable in PRs, synced with tc sync.
CLI utility to check if Git repo was vibe-coded or not
Handy CLI that actually pulls a repo and runs a battery of concrete heuristics — repo age, README keywords/emoji counts, commit velocity, presence of LLM-tool files, and simple commit-statistics — to guess whether code was prompt-expanded. The rule set is intentionally arbitrary and extensible, which makes this a useful starting point for audits or CI checks, but expect false positives and plan to tune or add rules for your context.
Developers, repository maintainers, code reviewers and security researchers who want to flag likely LLM-generated projects
Rules are pretty arbitrary and (with Rust) can be easily added for more checks in case anyone wants to contribute :)
Git-versioned team context for Claude Code teams; reviewable in PRs, synced with tc sync.
Context Repositories — treating agent memory like a git repo you can diff, branch, and version — is a clever, developer-friendly twist on long-term LLM state. Letta Code’s persisted, model‑agnostic agents and the Conversations API make the product feel like a coherent stack for production agents, though the trick will be real-world scale, merge semantics, and cost of storing rich context over time.
Bash wrapper around Claude API when CodeRabbit and Cursor already exist.
Native Rust IDE + agent pause-resume, but Cursor already does this with better market momentum.
OpenSCAD IDE with AI refactor, but parser is immature and audience is niche.
Yet another AI app directory when Product Hunt and existing platforms already do this.