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

How to carry project conventions into every new coding session with Semantix

Reuse build rules, test layout and service flags from past sessions instead of re-explaining them.

Authorization notice. Semantix is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. The install command pipes a script from GitHub straight into sh, so read agent-skill/scripts/install.sh before running it.

Credentials. The first run asks for a provider API key, so store it in your own environment and do not paste it into shared logs or prompts.

Who it is forA developer who restarts coding sessions on the same project and keeps re-stating build conventions, test commands and service flags.

The problemA coding agent loses its entire context when a session ends, so project conventions have to be re-established every time.

The outcomeRelevant slices from earlier sessions are pulled back into a new session when a similar task appears, with each hit showing its retrieval zone and source session.

What you need first

  • macOS or Linux on arm64 or amd64 for the one-line install
  • A model provider account and API key, set up on the first run of semantix
  • Go 1.26 or later only if you build from source
  • A session transcript in JSONL format for the extract and verify steps

Steps

  1. Run curl -fsSL https://raw.githubusercontent.com/Gnosil/semantix/main/agent-skill/scripts/install.sh | sh to install Semantix and semantix-agent into ~/.local/bin.
  2. Run cd ~/your-project to make the project folder the workspace.
  3. Run semantix to launch the coding agent and finish provider and API key setup on the first run.
  4. Run semantix extract --input session.jsonl --db .semantix/project.db --project demo on a finished session transcript.
  5. Run semantix inject --query "fix failing go test" --db .semantix/project.db to see the reuse block for a similar task. (inferred, check the README)

Prompt for your agent

Using the Gnosil/semantix repo, install it, extract slices from <session.jsonl> into .semantix/project.db, then run semantix inject with a query describing <task>. Report the slices returned with their retrieval zone and source session. Verify that each returned slice names a session that exists in <session.jsonl>.

Caveat. The README's 80% hit rate comes from a small demo library of 4 extracted sessions, so expect different results on your own project.

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