Repository Analysis

max-sixty/worktrunk

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

6.9 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of max-sixty/worktrunk, a Rust project with 6,731 GitHub stars. SynthScan v2.0 examined 306,282 lines of code across 456 source files, recording 1760 pattern matches distributed across 14 syntactic categories. The overall adjusted score of 6.9 places this repository in the Low AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

6.9
Adjusted Score
6.9
Raw Score
100%
Time Factor
2026-08-29
Last Push
6.7K
Stars
Rust
Language
306.3K
Lines of Code
456
Files
1.8K
Pattern Hits
2026-08-29
Scan Date
0.22
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 99MEDIUM 17LOW 1644

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 1760 distinct pattern matches across 14 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block1537 hits · 1434 pts
SeverityFileLineSnippetContext
LOWCargo.toml1[workspace]COMMENT
LOWCargo.toml121# Also install as git-wt so `git wt <command>` works as a git subcommand.COMMENT
LOWCargo.toml161# backup.rs) landed in chrono 0.4.31. `-Z minimal-versions` otherwise resolvesCOMMENT
LOWCargo.toml241sha2 = "0.11"COMMENT
LOWCargo.toml261# Interactive picker (`wt switch`) TUI stack, pulled in only by the `cli`COMMENT
LOWCargo.toml281# console — every picker PTY test failed with "Keyboard progressive enhancementCOMMENT
LOWdist-workspace.toml1[workspace]COMMENT
LOW.config/lychee.toml81COMMENT
LOW…ktrunk/skills/worktrunk/reference/shell-integration.md181# wt () { ... }COMMENT
LOWtests/cancel_background.rs1//! Cancellation of background commands (`worktrunk::shell_exec`).COMMENT
LOWtests/cancel_background.rs21///COMMENT
LOWtests/integration_tests/shell_integration_windows.rs1//! Windows-specific shell integration tests.COMMENT
LOWtests/integration_tests/completion_validation.rs41/// it to every user's shell.COMMENT
LOWtests/integration_tests/switch.rs481/// Since tests run via `cargo test`, argv[0] contains a path (`target/debug/wt`), whichCOMMENT
LOWtests/integration_tests/switch.rs581/// rev-parse --git-dir failed (exit 128)`.COMMENT
LOWtests/integration_tests/switch.rs721/// The `--execute` no-integration fallback relocates the payload into theCOMMENT
LOWtests/integration_tests/switch.rs761 );COMMENT
LOWtests/integration_tests/switch.rs2681 // meaningful on a platform where the mock `gh` might fail to resolve.COMMENT
LOWtests/integration_tests/switch.rs2741 log_entry["bytes"].as_u64().unwrap_or(0) > 0,COMMENT
LOWtests/integration_tests/switch.rs2961/// calls keyed by the row's structured MR identity. Both `mode:4` (Log) and `mode:8`COMMENT
LOWtests/integration_tests/switch.rs3281/// Test same-repo PR when origin points to a different repo (no remote for PR's repo)COMMENT
LOWtests/integration_tests/switch.rs3521}COMMENT
LOWtests/integration_tests/switch.rs3861 });COMMENT
LOWtests/integration_tests/switch.rs5941 settings.bind(|| {COMMENT
LOWtests/integration_tests/switch.rs7701/// `.git` file of linked worktrees instead of absolute paths. This makes worktreeCOMMENT
LOWtests/integration_tests/for_each.rs201/// the wt process. Sending SIGINT to the parent wt process from an integrationCOMMENT
LOWtests/integration_tests/remove.rs401COMMENT
LOWtests/integration_tests/remove.rs521 NoneCOMMENT
LOWtests/integration_tests/remove.rs541 assert_cmd_snapshot!(make_snapshot_cmd(&repo, "remove", &["feature"], None));COMMENT
LOWtests/integration_tests/remove.rs601 worktree.join(path)COMMENT
LOWtests/integration_tests/remove.rs1601/// 2. Squash-merge feature into main (main now has A via squash commit)COMMENT
LOWtests/integration_tests/remove.rs1701/// This is the scenario from issue #1818:COMMENT
LOWtests/integration_tests/remove.rs1781 ));COMMENT
LOWtests/integration_tests/remove.rs2161///COMMENT
LOWtests/integration_tests/remove.rs2641 );COMMENT
LOWtests/integration_tests/remove.rs2721 Some(&worktree_path)COMMENT
LOWtests/integration_tests/remove.rs2961COMMENT
LOWtests/integration_tests/remove.rs3001COMMENT
LOWtests/integration_tests/remove.rs3321}COMMENT
LOWtests/integration_tests/remove.rs3561/// touched (100+ is routine) once paid one `lsof` spawn each on everyCOMMENT
LOWtests/integration_tests/remove.rs3641 );COMMENT
LOWtests/integration_tests/remove.rs4061 cmdCOMMENT
LOWtests/integration_tests/remove.rs4221}COMMENT
LOWtests/integration_tests/remove.rs4321}COMMENT
LOWtests/integration_tests/security.rs1//! Security tests for shell injection vulnerabilitiesCOMMENT
LOWtests/integration_tests/security.rs21//! file is only written by Rust code, never by external content.COMMENT
LOWtests/integration_tests/security.rs41//!COMMENT
LOWtests/integration_tests/security.rs361/// at the ref validation level: control characters (bytes < 0x20 or 0x7F)COMMENT
LOWtests/integration_tests/list.rs1341 repo.run_git(&["add", "README.md", "lib.rs"]);COMMENT
LOWtests/integration_tests/list.rs1501///COMMENT
LOWtests/integration_tests/list.rs1521///COMMENT
LOWtests/integration_tests/list.rs2521COMMENT
LOWtests/integration_tests/list.rs3321COMMENT
LOWtests/integration_tests/list.rs3701///COMMENT
LOWtests/integration_tests/list.rs3721 std::fs::write(&ref_path, "0000000000000000000000000000000000000001\n").unwrap();COMMENT
LOWtests/integration_tests/list.rs3821COMMENT
LOWtests/integration_tests/list.rs4021/// matching `Repository::integration_reason`. A branch whose content lives inCOMMENT
LOWtests/integration_tests/list.rs4381 use std::os::unix::fs::PermissionsExt;COMMENT
LOWtests/integration_tests/ci_status.rs501 settings.bind(|| {COMMENT
LOWtests/integration_tests/ci_status.rs1341/// nothing about being an error, and a proxy's HTML page isn't Gitea's shape atCOMMENT
1477 more matches not shown…
Cross-File Repetition84 hits · 420 pts
SeverityFileLineSnippetContext
HIGH…ns/worktrunk/skills/worktrunk/reference/llm-commits.md0write a commit message for this diff. one line, under 50 chars. branch: {{ branch }} diff: {{ git_diff }}STRING
HIGHdocs/public/llm-commits.md0write a commit message for this diff. one line, under 50 chars. branch: {{ branch }} diff: {{ git_diff }}STRING
HIGHdocs/src/content/docs/llm-commits.md0write a commit message for this diff. one line, under 50 chars. branch: {{ branch }} diff: {{ git_diff }}STRING
HIGHskills/worktrunk/reference/llm-commits.md0write a commit message for this diff. one line, under 50 chars. branch: {{ branch }} diff: {{ git_diff }}STRING
HIGH…ns/worktrunk/skills/worktrunk/reference/llm-commits.md0combine these {{ commit_details | length }} commits into one message: {% for c in commit_details %} - {{ c.subject }} {%STRING
HIGHdocs/public/llm-commits.md0combine these {{ commit_details | length }} commits into one message: {% for c in commit_details %} - {{ c.subject }} {%STRING
HIGHdocs/src/content/docs/llm-commits.md0combine these {{ commit_details | length }} commits into one message: {% for c in commit_details %} - {{ c.subject }} {%STRING
HIGHskills/worktrunk/reference/llm-commits.md0combine these {{ commit_details | length }} commits into one message: {% for c in commit_details %} - {{ c.subject }} {%STRING
HIGH…ns/worktrunk/skills/worktrunk/reference/llm-commits.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/public/llm-commits.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/src/content/docs/llm-commits.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHskills/worktrunk/reference/llm-commits.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHplugins/worktrunk/skills/worktrunk/reference/config.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/public/config.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/src/content/docs/config.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHskills/worktrunk/reference/config.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHsrc/cli/mod.rs0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdev/wt.example.toml0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGH…gins/worktrunk/skills/worktrunk/reference/extending.md0git fetch --all --prune; wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-parSTRING
HIGHdocs/public/extending.md0git fetch --all --prune; wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-parSTRING
HIGHdocs/src/content/docs/extending.md0git fetch --all --prune; wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-parSTRING
HIGHskills/worktrunk/reference/extending.md0git fetch --all --prune; wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-parSTRING
HIGH…gins/worktrunk/skills/worktrunk/reference/extending.md0if git diff --quiet head && test -z "$(git ls-files --others --exclude-standard)"; then wt switch --create {{ to }} --exSTRING
HIGHdocs/public/extending.md0if git diff --quiet head && test -z "$(git ls-files --others --exclude-standard)"; then wt switch --create {{ to }} --exSTRING
HIGHdocs/src/content/docs/extending.md0if git diff --quiet head && test -z "$(git ls-files --others --exclude-standard)"; then wt switch --create {{ to }} --exSTRING
HIGHskills/worktrunk/reference/extending.md0if git diff --quiet head && test -z "$(git ls-files --others --exclude-standard)"; then wt switch --create {{ to }} --exSTRING
HIGH…gins/worktrunk/skills/worktrunk/reference/extending.md0tail -f "$(wt config state logs --format=json | jq -r --arg name "{{ name | sanitize_hash }}" --arg kind "{{ kind }}" ' STRING
HIGHdocs/public/extending.md0tail -f "$(wt config state logs --format=json | jq -r --arg name "{{ name | sanitize_hash }}" --arg kind "{{ kind }}" ' STRING
HIGHdocs/src/content/docs/extending.md0tail -f "$(wt config state logs --format=json | jq -r --arg name "{{ name | sanitize_hash }}" --arg kind "{{ kind }}" ' STRING
HIGHskills/worktrunk/reference/extending.md0tail -f "$(wt config state logs --format=json | jq -r --arg name "{{ name | sanitize_hash }}" --arg kind "{{ kind }}" ' STRING
HIGHplugins/worktrunk/skills/worktrunk/reference/config.md0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHdocs/public/config.md0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHdocs/src/content/docs/config.md0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHskills/worktrunk/reference/config.md0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHsrc/cli/mod.rs0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHdev/config.example.toml0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHplugins/worktrunk/skills/worktrunk/reference/config.md0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHdocs/public/config.md0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHdocs/src/content/docs/config.md0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHskills/worktrunk/reference/config.md0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHsrc/cli/mod.rs0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHdev/config.example.toml0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHplugins/worktrunk/skills/worktrunk/reference/config.md0# - explain the rationale in the body, not just the change #STRING
HIGHdocs/public/config.md0# - explain the rationale in the body, not just the change #STRING
HIGHdocs/src/content/docs/config.md0# - explain the rationale in the body, not just the change #STRING
HIGHskills/worktrunk/reference/config.md0# - explain the rationale in the body, not just the change #STRING
HIGHsrc/cli/mod.rs0# - explain the rationale in the body, not just the change #STRING
HIGHdev/config.example.toml0# - explain the rationale in the body, not just the change #STRING
HIGH…/worktrunk/skills/worktrunk/reference/tips-patterns.md0wt config state vars set \ container='{{ repo }}-{{ branch | sanitize }}-postgres' \ port='{{ ('db-' ~ branch) | hash_poSTRING
HIGHdocs/public/tips-patterns.md0wt config state vars set \ container='{{ repo }}-{{ branch | sanitize }}-postgres' \ port='{{ ('db-' ~ branch) | hash_poSTRING
HIGHdocs/src/content/docs/tips-patterns.md0wt config state vars set \ container='{{ repo }}-{{ branch | sanitize }}-postgres' \ port='{{ ('db-' ~ branch) | hash_poSTRING
HIGHskills/worktrunk/reference/tips-patterns.md0wt config state vars set \ container='{{ repo }}-{{ branch | sanitize }}-postgres' \ port='{{ ('db-' ~ branch) | hash_poSTRING
HIGH…/worktrunk/skills/worktrunk/reference/tips-patterns.md0docker run -d --rm \ --name {{ vars.container }} \ -p {{ vars.port }}:5432 \ -e postgres_db={{ branch | sanitize_db }} \STRING
HIGHdocs/public/tips-patterns.md0docker run -d --rm \ --name {{ vars.container }} \ -p {{ vars.port }}:5432 \ -e postgres_db={{ branch | sanitize_db }} \STRING
HIGHdocs/src/content/docs/tips-patterns.md0docker run -d --rm \ --name {{ vars.container }} \ -p {{ vars.port }}:5432 \ -e postgres_db={{ branch | sanitize_db }} \STRING
HIGHskills/worktrunk/reference/tips-patterns.md0docker run -d --rm \ --name {{ vars.container }} \ -p {{ vars.port }}:5432 \ -e postgres_db={{ branch | sanitize_db }} \STRING
HIGH…/worktrunk/skills/worktrunk/reference/tips-patterns.md0f=$(mktemp); printf '\n\n' > "$f"; sed 's/^/# /' >> "$f"; ${editor:-vi} "$f" < /dev/tty > /dev/tty; grep -v '^#' "$f"STRING
HIGHdocs/public/tips-patterns.md0f=$(mktemp); printf '\n\n' > "$f"; sed 's/^/# /' >> "$f"; ${editor:-vi} "$f" < /dev/tty > /dev/tty; grep -v '^#' "$f"STRING
HIGHdocs/src/content/docs/tips-patterns.md0f=$(mktemp); printf '\n\n' > "$f"; sed 's/^/# /' >> "$f"; ${editor:-vi} "$f" < /dev/tty > /dev/tty; grep -v '^#' "$f"STRING
HIGHskills/worktrunk/reference/tips-patterns.md0f=$(mktemp); printf '\n\n' > "$f"; sed 's/^/# /' >> "$f"; ${editor:-vi} "$f" < /dev/tty > /dev/tty; grep -v '^#' "$f"STRING
24 more matches not shown…
Synthetic Comment Markers14 hits · 72 pts
SeverityFileLineSnippetContext
HIGHREADME.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHREADME.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGH…gins/worktrunk/skills/worktrunk/reference/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGH…gins/worktrunk/skills/worktrunk/reference/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHplugins/worktrunk/skills/worktrunk/reference/README.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHplugins/worktrunk/skills/worktrunk/reference/README.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHdocs/public/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHdocs/public/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHdocs/src/content/docs/worktrunk.md104- **[`wt list --full`](/list/#full-mode)** — [CI status](/list/#ci-status) and [AI-generated summaries](/list/#llm-summaCODE
HIGHskills/worktrunk/reference/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHskills/worktrunk/reference/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHskills/worktrunk/reference/README.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHskills/worktrunk/reference/README.md94- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHsrc/commands/statusline.rs920 // What the schema-2 envelope reports as requested — read from the taskCOMMENT
Verbosity Indicators31 hits · 52 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/switch.rs1976 // Step 2: From ping-pong worktree, switch back to mainCOMMENT
LOWtests/integration_tests/switch.rs1985 // Step 3: From main worktree, wt switch - should go to ping-pongCOMMENT
LOWtests/integration_tests/switch.rs1994 // Step 4: From ping-pong worktree, wt switch - should go back to mainCOMMENT
LOWtests/integration_tests/switch.rs1998 // Step 5: From main worktree, wt switch - should go to ping-pong again (ping-pong!)COMMENT
LOWtests/integration_tests/switch.rs7566 // Step 2: Switch to hist-feature again while already there (AlreadyAt)COMMENT
LOWtests/integration_tests/switch.rs7575 // Step 3: `wt switch -` should still go to main (the real previous),COMMENT
LOWtests/integration_tests/switch.rs1961 // Step 1: From main worktree, switch to ping-pong (creates worktree)COMMENT
LOWtests/integration_tests/switch.rs7554 // Step 1: Switch from main to hist-feature (establishes history: previous=main)COMMENT
LOWtests/integration_tests/list.rs108 // Step 1: From main, switch to feature (history: current=feature, previous=main)COMMENT
LOWtests/integration_tests/list.rs115 // Step 2: From feature, switch back to main (history: current=main, previous=feature)COMMENT
LOWtests/integration_tests/readme_sync.rs2707 // Step 0: Fill docs-example bodies in src/cli/mod.rs from snapshots. RunsSTRING
LOWtests/integration_tests/readme_sync.rs2713 // Step 1: Sync command pages into the Starlight content collection.STRING
LOWtests/integration_tests/readme_sync.rs2717 // Step 2: Sync standalone docs files from snapshots.STRING
LOWtests/integration_tests/readme_sync.rs2743 // Step 3: Sync skill files (Starlight Markdown → skills/*)STRING
LOWtests/integration_tests/readme_sync.rs2752 // Step 4: Sync .well-known/agent-skills/ (skills/ → docs/public/)STRING
LOWtests/integration_tests/readme_sync.rs2756 // Step 5: Generate docs/public/llms.txt from Starlight frontmatter.STRING
LOWtests/integration_tests/readme_sync.rs2767 // Step 6: Sync README from the now-fresh docs files. Runs last becauseSTRING
LOWtests/integration_tests/shell_wrapper.rs2750# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2757# Step 2: Get the completion function name (whatever it's called)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2765# Step 3: Set up completion environment and call the functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2775# Step 4: Verify we got completions (black-box: just check we got results)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2885# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2894# Step 2: Test that COMPLETE mode works through our shell functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2788# Step 5: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2916# Step 3: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/approval_pty.rs752 // Step 1: project config with only the hook; pre-approve it.COMMENT
LOWtests/integration_tests/approval_pty.rs764 // Step 2: add an unapproved commit append (hook command unchanged, so itCOMMENT
LOWsrc/llm.rs317 // Step 1: Filter out lock filesCOMMENT
LOWsrc/llm.rs349 // Step 2: Truncate each section, accumulating until the budget is spentCOMMENT
LOWsrc/commands/list/ci_status/gitlab.rs125 // Step 1: Parse mr list output to find matching MR.COMMENT
LOWsrc/commands/list/ci_status/gitlab.rs166 // Step 2: Fetch full MR details to get pipeline status.COMMENT
Structural Annotation Overuse31 hits · 51 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/switch.rs1976 // Step 2: From ping-pong worktree, switch back to mainCOMMENT
LOWtests/integration_tests/switch.rs1985 // Step 3: From main worktree, wt switch - should go to ping-pongCOMMENT
LOWtests/integration_tests/switch.rs1994 // Step 4: From ping-pong worktree, wt switch - should go back to mainCOMMENT
LOWtests/integration_tests/switch.rs1998 // Step 5: From main worktree, wt switch - should go to ping-pong again (ping-pong!)COMMENT
LOWtests/integration_tests/switch.rs7566 // Step 2: Switch to hist-feature again while already there (AlreadyAt)COMMENT
LOWtests/integration_tests/switch.rs1961 // Step 1: From main worktree, switch to ping-pong (creates worktree)COMMENT
LOWtests/integration_tests/switch.rs7554 // Step 1: Switch from main to hist-feature (establishes history: previous=main)COMMENT
LOWtests/integration_tests/list.rs108 // Step 1: From main, switch to feature (history: current=feature, previous=main)COMMENT
LOWtests/integration_tests/list.rs115 // Step 2: From feature, switch back to main (history: current=main, previous=feature)COMMENT
LOWtests/integration_tests/list.rs1537/// NOTE: This function is used for doc generation. It removes fixture worktreesCOMMENT
LOWtests/integration_tests/readme_sync.rs2707 // Step 0: Fill docs-example bodies in src/cli/mod.rs from snapshots. RunsSTRING
LOWtests/integration_tests/readme_sync.rs2713 // Step 1: Sync command pages into the Starlight content collection.STRING
LOWtests/integration_tests/readme_sync.rs2717 // Step 2: Sync standalone docs files from snapshots.STRING
LOWtests/integration_tests/readme_sync.rs2743 // Step 3: Sync skill files (Starlight Markdown → skills/*)STRING
LOWtests/integration_tests/readme_sync.rs2752 // Step 4: Sync .well-known/agent-skills/ (skills/ → docs/public/)STRING
LOWtests/integration_tests/readme_sync.rs2756 // Step 5: Generate docs/public/llms.txt from Starlight frontmatter.STRING
LOWtests/integration_tests/readme_sync.rs2767 // Step 6: Sync README from the now-fresh docs files. Runs last becauseSTRING
LOWtests/integration_tests/shell_wrapper.rs2750# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2757# Step 2: Get the completion function name (whatever it's called)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2765# Step 3: Set up completion environment and call the functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2775# Step 4: Verify we got completions (black-box: just check we got results)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2885# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2894# Step 2: Test that COMPLETE mode works through our shell functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2788# Step 5: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2916# Step 3: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/approval_pty.rs752 // Step 1: project config with only the hook; pre-approve it.COMMENT
LOWtests/integration_tests/approval_pty.rs764 // Step 2: add an unapproved commit append (hook command unchanged, so itCOMMENT
LOWsrc/llm.rs317 // Step 1: Filter out lock filesCOMMENT
LOWsrc/llm.rs349 // Step 2: Truncate each section, accumulating until the budget is spentCOMMENT
LOWsrc/commands/list/ci_status/gitlab.rs125 // Step 1: Parse mr list output to find matching MR.COMMENT
LOWsrc/commands/list/ci_status/gitlab.rs166 // Step 2: Fetch full MR details to get pipeline status.COMMENT
Unused Imports33 hits · 26 pts
SeverityFileLineSnippetContext
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py3CODE
LOWdocs/demos/shared/__init__.py39CODE
LOWdocs/demos/shared/__init__.py39CODE
LOWdocs/demos/shared/validation.py23CODE
AI Slop Vocabulary9 hits · 25 pts
SeverityFileLineSnippetContext
MEDIUMtests/integration_tests/switch_picker_dry_run.rs107 // schema (not specific branches/modes) keeps the test robust to fixtureCOMMENT
MEDIUMtests/common/pty.rs51 // this is the more robust replacement.COMMENT
MEDIUMdocs/demos/shared/lib.py806 """Set up comprehensive mock CLIs for all demo scenarios.STRING
MEDIUM.github/workflows/benchmarks.yaml9# harness still builds — create-issue-on-benchmark-failure surfaces a break.COMMENT
MEDIUM.github/workflows/tend-notifications.yaml83 # Event workflows mark their own notifications read via the harnessCOMMENT
MEDIUM.github/workflows/tend-review.yaml112 # containment the harness builds for the contributor's code.COMMENT
MEDIUMsrc/commands/process.rs681/// just makes its cleanup robust.COMMENT
MEDIUMsrc/commands/list/collect/mod.rs293//! ### Fundamentally uncacheableCOMMENT
MEDIUMsrc/commands/list/collect/mod.rs293//! ### Fundamentally uncacheableCOMMENT
Decorative Section Separators4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMtests/integration_tests/step_promote.rs390// ─── Swap tests ───────────────────────────────────────────────────────────COMMENT
MEDIUMdocs/demos/shared/lib.py1075# =============================================================================COMMENT
MEDIUMdocs/demos/shared/lib.py1077# =============================================================================COMMENT
MEDIUMsrc/git/repository/integration.rs1038 /// └────── squash ── pad1 ── … ── padN = target (each pad reuses parent's tree)COMMENT
Hyper-Verbose Identifiers7 hits · 7 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/shell_wrapper.rs2462def test_login_invalid_password():CODE
LOWdocs/demos/tests/test_recording.py16def test_each_theme_records_from_a_fresh_environment(tmp_path: Path) -> None:CODE
LOWdocs/demos/tests/test_recording.py72def test_docs_demos_open_on_a_complete_command_before_execution() -> None:CODE
LOWdocs/demos/tests/test_recording.py104def test_docs_demos_hide_all_setup_and_cleanup_from_the_recording() -> None:CODE
LOWdocs/demos/tests/test_recording.py127def test_mobile_core_demo_has_a_readable_dedicated_recording_contract() -> None:CODE
LOWdocs/demos/shared/lib.py1180def extract_commands_from_tape(CODE
LOWdocs/demos/shared/validation.py378def validate_tui_demo_verbose(demo_name: str, gif_path: Path) -> tuple[bool, str]:CODE
Self-Referential Comments3 hits · 7 pts
SeverityFileLineSnippetContext
MEDIUMdocs/demos/shared/lib.py508 "# This file contains fish universal variable definitions.",STRING
MEDIUM.github/workflows/release.yaml345 # Create a GitHub Release while uploading all files to itCOMMENT
MEDIUMsrc/cli/mod.rs626## Creating a branchCOMMENT
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/shell_wrapper.rs1907 # Check if wt completion is registered and write result to marker fileCOMMENT
LOWtests/integration_tests/shell_wrapper.rs1958 # Check if wt completions are registered and write result to marker fileCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2015 # Check if wt wrapper function is defined and write result to marker fileCOMMENT
LOW.github/workflows/ci.yaml170 # Check if Cargo/CI files changed (for conditional jobs below)COMMENT
Cross-Language Confusion1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHdocs/demos/shared/lib.py796 set -l branch (git rev-parse --abbrev-ref HEAD 2>/dev/null)CODE
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml187# scaffolding; `registry` composes layers. Pinned to ≥ 0.3.17: that's whenCOMMENT
Modern Structural Boilerplate1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/demos/shared/__init__.py41__all__ = [CODE