DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find existing code for a service before writing it again with Session Knowledge

Search past projects by external service tag to see whether the integration already exists.

Who it is forA developer about to add a payment, auth, or messaging integration who suspects it was already built in another project.

The problemgrep only finds code if you already know the function or token name, so existing integrations are easy to miss and get rebuilt.

The outcomeA list of existing implementations for the service, found by capability tag, before any new code is written.

What you need first

  • Claude Code with session transcripts in ~/.claude/projects/
  • Python 3.10+ with FTS5 in the bundled sqlite3 (on macOS, install from python.org or run brew install python)
  • git and bash to clone and run install.sh
  • Terminal access to run the CLI and restart Claude Code

Steps

  1. git clone https://github.com/nameforjt-afk/session-knowledge.git
  2. cd session-knowledge then bash install.sh
  3. Restart Claude Code.
  4. python3 -m sessionmcp.cli index
  5. python3 -m sessionmcp.cli code find --capability stripe

Prompt for your agent

In the session-knowledge repo, call find_implementation with capability <service-name> before writing new integration code. Expect a list of existing implementations with their file paths. Verify that one returned file still exists on disk before reusing it.

Caveat. The code index only reads Python, JS, and TS files and only scans projects with at least 2 sessions in the last 45 days, so a service built in another language or a one-session project will not appear.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page