Introduction

Truemend reads your codebase on your machine. It names what is not production-ready, applies the mechanical fixes as diffs you can review, and leaves the rest for a person, with evidence attached. Validation checks do not prove that a change preserves every aspect of application behavior, so review diffs and run your tests before merging.

What Truemend does

1. Reads the supported files in the directory you point it at and scores the functions it finds
2. Names each finding and files it by fix path: patch, refactor or rewrite
3. Fixes the mechanical ones automatically, then re-parses the file to check it still parses
4. Reports per-function quality scores, rolled up into families

How it works

• No model in detection. Findings come from the code, not from a guess.
• Function-level. Scores and findings are per-function, not one verdict per file.
• Reversible fixes. If a change leaves the file unable to parse, the original is restored.
• Where the code already is. Terminal, editor, pull request, and the coding assistant you already use.