Alternatives
Products that do what RepairTracking does
RepairTracking est un logiciel de suivi de réparation
- 1
Smart for repair shop management with dynamic QR tracking
Jun 2026 · repairtracks.online
- 2
- 3
- 4
- 5
- 6
- 7
- 8
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com
- 9FL
2023 · useadrenaline.com
- 10
- 11
- 12
- 13
- 14
- 15AA
Athelas reads stacktraces and comments, taking into account potential logic errors, to automagically repair broken code.
2023 · huggingface.co
- 16
- 17FR
I built FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self-hosted VSCode extension and as a Github app: VSCode Extension: https://fixbugs.ai/go/vscode-extension - full code and data privacy. - zero data retention models opted out of training. GitHub App: https://fixbugs.ai/go/github-app - we do access your code temporarily. - pick a repo to install FixBugs on. What motivated me to build FixBugs were my years being on-call at Google…
Jul 2026 · fixbugs.ai
- 18IB
2024 · securelog.com
- 19TS
Hi HN! We’re Ethan and Danny, the authors of Tangent (https://github.com/telophasehq/tangent), a Rust-based log pipeline where all normalization, enrichment, and detection logic runs as WASM plugins. We kept seeing the same problems in the OCSF (https://ocsf.io) community: 1) Schemas change constantly. Large companies have whole teams dedicated to keeping vendor→OCSF mappings up to date. 2) There’s no shared library of mappings, so everyone recreates the same work. 3) Writing mappers is tedious, repetitive work. 4) Most pipelines use proprietary DSLs that are…
Nov 2025 · github.com
- 20
- 21RR
Nathan here, one of the people who built Retrace. Happy to answer technical questions. Retrace records a CPython application's interactions with the nondeterministic outside world i.e. network, DB, filesystem, time, randomness, subprocesses, and lets you replay that execution locally and deterministically. The goal is to take a production failure and open the same execution in VS Code, with the ability to step forwards and backwards through the replay. The core idea is to record boundary crossings rather than tracing every Python line in production. External calls are recorded as…
May 2026 · github.com
- 22
I kept generating slide decks about my codebases with an agent, and weeks later they would go stale. Updating them was quite costly (time & tokens), as the agent would have to re-scan the whole repo to re-generate the slides. So I made the slide deck carry its own provenance: SlideOps skill turns a repo into a slide deck, with all references to files carrying exact line range and a hash. Checking is done with standard-library Python: no model calls, no network, and very fast. For example, it distinguishes MOVED (the code shifted) from CHANGED (the content differs). Updating the slides costs…
6d ago · github.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →