Reviews can be signed by known PGP keys, and this can extend/scale into a network of trusted code. For example, open source libraries could accumulate layers of reviews from many individuals (across companies), and we can cryptographically verify who reviewed what.
- [ ] Add a small “reviewed!” animation in review mode when approving/commenting.
- [ ] Show reviewed vs remaining counts in bottom-right (e.g., 5 / 15), with green reviewed and yellow remaining.
- [ ] Implement side-by-side view (Diff vs New Content).
- [ ] **Complex:** Implement true inline editing where changes in the review buffer apply to the file.
- Draft Plan: Use `ediff` or a custom overlay that writes back to file on `C-c C-c`.
- Alternative: Use `recursive-edit` in the file buffer.
- [ ] Encapsulate generation of `Uuid`, `SystemTime`, and `CURRENT_VERSION` in `Record::new` to simplify `mark.rs`.
- [ ] Optimize verification by maintaining a `HashSet` of imported key fingerprints to avoid redundant `gpg –import` calls.
- [ ] Extract `GpgClient` to handle temp dir lifecycle and provide high-level `sign` and `verify` methods.
- [ ] Add `trueflow coverage` command that shells out to `cargo llvm-cov` or `just coverage`.
- [ ] Add coverage mode to show least-reviewed files.
- [ ] Add per-file heatmap (red = unreviewed, blue = well-reviewed).
- [ ] Add an overlay/command to show reviewed vs unreviewed lines and coverage.
- [ ] Extend coverage to code paths/branches where possible.
- [ ] Model how well reviewed a codepath is using AST relationships.
- [ ] Compute a complexity score per block to trigger review thresholds.
- [ ] Add top 16 languages/markdown variants.
- [ ] Add an `all_langs` repo fixture and E2E smoke tests per language.
- [ ] Add Swift language support for common review units: imports, structs/classes/enums, protocols, extensions, methods, and tests.
- [ ] Add Swift fixtures and E2E review-generation tests covering realistic review cases.
- [ ] Verify review UX for Swift-specific patterns like protocol conformance changes, extension-heavy files, and SwiftUI view bodies.
- [ ] Support review types (security, dependencies, performance, readability, data structures, business logic).
- [ ] Tag reviews with a type and make modes affect block ordering and filters (e.g., data structures shows structs).
- [ ] Fetch/check out PRs, map review targets to the right diff, and post feedback as comments.
- [ ] Call a local model to explain context behind a change.
- [ ] Evaluate high-quality Rust lints (deny, udeps, semver-checks, geiger, nextest) and wire into `just check`.
- [ ] Formalize a high-quality install plan (cargo install vs curl | sh vs package managers).
code block area and controls in TUI
“` struct #[derive(Debug, Clone)] in ./example_repos/all_languages/main.rs (hash=a85ccbc9), subblocks: └─ CodeParagraph
#[derive(Debug, Clone)] struct Config { name: String, threshold: i32, } “` Two things:
- struct #[derive(Debug, Clone)] is wrong, should be struct Config
- Let’s make the output a little nicer to read: (no ./) example_repos/all_languages/main.rs -> struct Config (hash=a85ccbc9) {directly embed the subblock tree here}
current user for the current REV. i.e. delete all review records that point to the current rev. (without removing historical reviews, etc.)
reverse-chronological order, like a trueflow log command, defaults to say the most recent 16 or something.
- [ ] Define and verify how we present textual diff chunks versus reconstructed new content.
- [ ] Explore how Jujutsu can improve diffing, review, and syncing flows.
- [ ] Add landing page, user docs, and onboarding guide.
- [ ] Ship a fully static musl build.
- [ ] Audit dependencies; prefer pure Rust and reduce OpenSSL/FFI usage.
- [ ] Spin up Vultr infra and document deployment via the org meta repo.
- [ ] Audit for performance improvements and implement top candidates.
j back sentence; l forward sentence
[HIGH] please move the pgup/down, and [h]prev next down up to the right side of the navigation legend. parent and child can be in the middle. on the left, approve and comment, then mode. quit stays on furthest right. please confirm the order and layout with me.
** TODO [HIGH] off-by-1 in progress bar. seems to include summary page at end of review.