Repository Analysis

max-sixty/worktrunk

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

7.0 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of max-sixty/worktrunk, a Rust project with 5,821 GitHub stars. SynthScan v2.0 examined 274,694 lines of code across 462 source files, recording 1529 pattern matches distributed across 16 syntactic categories. The overall adjusted score of 7.0 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).

7.0
Adjusted Score
7.0
Raw Score
100%
Time Factor
2026-07-14
Last Push
5.8K
Stars
Rust
Language
274.7K
Lines of Code
462
Files
1.5K
Pattern Hits
2026-07-14
Scan Date
0.21
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 18LOW 1412

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 1529 distinct pattern matches across 16 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 Block1308 hits · 1228 pts
SeverityFileLineSnippetContext
LOWCargo.toml1[workspace]COMMENT
LOWCargo.toml101# Enable shell/PTY integration tests (requires bash, zsh, fish installed on system)COMMENT
LOWCargo.toml161# `unstable-markdown` renders our `///` doc-comments as styled help (bold inlineCOMMENT
LOWCargo.toml241# can silently shift every existing user's codename-derived worktree path,COMMENT
LOWCargo.toml261wait-timeout = "0.2"COMMENT
LOWCargo.toml281# to build).COMMENT
LOWdist-workspace.toml1[workspace]COMMENT
LOW.config/lychee.toml81 "wt-demo/out/wt-demo\\.gif",COMMENT
LOW.config/nextest.toml1# IMPORTANT: Tests that spawn interactive shells (zsh -ic, bash -ic) causeCOMMENT
LOW.config/nextest.toml21success-output = "never"COMMENT
LOW.config/nextest.toml41# and pass it through with --target-dir. Worktrunk already requires bash forCOMMENT
LOWtests/integration_tests/shell_integration_windows.rs1//! Windows-specific shell integration tests.COMMENT
LOWtests/integration_tests/switch.rs421///COMMENT
LOWtests/integration_tests/switch.rs581/// The `--execute` no-integration fallback relocates the payload into theCOMMENT
LOWtests/integration_tests/switch.rs1861COMMENT
LOWtests/integration_tests/switch.rs2401 // row was created with the token `pr:42`, which seeds its preview cache. TheCOMMENT
LOWtests/integration_tests/switch.rs2461 .find(|e| e["branch"] == "pr:42" && e["mode"] == 2)COMMENT
LOWtests/integration_tests/switch.rs2681/// GitLab counterpart of the GitHub `_log_tab` / `_comments_tab` dry-run tests:COMMENT
LOWtests/integration_tests/switch.rs3421COMMENT
LOWtests/integration_tests/switch.rs5401//COMMENT
LOWtests/integration_tests/switch.rs6961/// directories relocatable. Older Git versions may still write absolute links,COMMENT
LOWtests/integration_tests/for_each.rs201/// the wt process. Sending SIGINT to the parent wt process from an integrationCOMMENT
LOWtests/integration_tests/remove.rs301}COMMENT
LOWtests/integration_tests/remove.rs1121 NoneCOMMENT
LOWtests/integration_tests/remove.rs1241 cmd.args(["remove", "-D", "main"])COMMENT
LOWtests/integration_tests/remove.rs1341 assert_cmd_snapshot!(make_snapshot_cmd(COMMENT
LOWtests/integration_tests/remove.rs2281 assert!(COMMENT
LOWtests/integration_tests/remove.rs2561 ));COMMENT
LOWtests/integration_tests/remove.rs2601 ));COMMENT
LOWtests/integration_tests/remove.rs2921 !String::from_utf8_lossy(&list.stdout).contains("feature--double-dash")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//! 1. Branch names with shell metacharacters don't corrupt the cd pathCOMMENT
LOWtests/integration_tests/security.rs381 "Malicious code was executed alongside legitimate -x command!"COMMENT
LOWtests/integration_tests/list.rs1101 // Test with compound emoji (multi-codepoint)COMMENT
LOWtests/integration_tests/list.rs1341/// **Project context**: API modernization — migrating from legacy handlers to REST,COMMENT
LOWtests/integration_tests/list.rs1361/// - `+25 -11` main…± — Deleted insecure validation, added proper checksCOMMENT
LOWtests/integration_tests/list.rs2781 // Expected order: main, feature-current, then by timestamp: feature-newest, feature-middle, feature-oldestCOMMENT
LOWtests/integration_tests/list.rs3341COMMENT
LOWtests/integration_tests/list.rs3441/// branch doesn't exist locally, `wt list` degrades gracefully — columns needingCOMMENT
LOWtests/integration_tests/list.rs3481COMMENT
LOWtests/integration_tests/list.rs3641/// case covered by `test_list_integrated_when_squash_merged_on_remote_with_local_diverged`COMMENT
LOWtests/integration_tests/ci_status.rs121// =============================================================================COMMENT
LOWtests/integration_tests/ci_status.rs641 repo.configure_mock_commands(&mut cmd);COMMENT
LOWtests/integration_tests/ci_status.rs901}COMMENT
LOWtests/integration_tests/bare_repository.rs281 expected_path.exists(),COMMENT
LOWtests/integration_tests/bare_repository.rs381/// Companion to `test_bare_repo_repo_path_with_inherited_relative_git_dir`COMMENT
LOWtests/integration_tests/bare_repository.rs601}COMMENT
LOWtests/integration_tests/bare_repository.rs801 contentCOMMENT
LOWtests/integration_tests/statusline.rs701//COMMENT
LOW…sts/integration_tests/column_alignment_verification.rs1//! Column Alignment Verification TestsCOMMENT
LOWtests/integration_tests/completion.rs461/// This captures the tension between #1468 (fish/zsh need all candidates forCOMMENT
LOWtests/integration_tests/readme_sync.rs1//! README and config synchronization testsCOMMENT
LOWtests/integration_tests/readme_sync.rs121 .unwrap()COMMENT
LOWtests/integration_tests/readme_sync.rs381// =============================================================================COMMENT
LOWtests/integration_tests/readme_sync.rs441 }COMMENT
LOWtests/integration_tests/readme_sync.rs1061///COMMENT
LOWtests/integration_tests/readme_sync.rs1921 result.push('\n');COMMENT
LOWtests/integration_tests/readme_sync.rs2201 }COMMENT
LOWtests/integration_tests/readme_sync.rs2381/// 1. placeholder idCOMMENT
1248 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/content/llm-commits.md0write a commit message for this diff. one line, under 50 chars. branch: {{ branch }} diff: {{ git_diff }}STRING
HIGHdocs/static/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/content/llm-commits.md0combine these {{ commit_details | length }} commits into one message: {% for c in commit_details %} - {{ c.subject }} {%STRING
HIGHdocs/static/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/content/llm-commits.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/static/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/content/config.md0# - use conventional commits (feat:, fix:, docs:, …) # - reference the relevant issue id in the body #STRING
HIGHdocs/static/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-pSTRING
HIGHdocs/content/extending.md0git fetch --all --prune && wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-pSTRING
HIGHdocs/static/extending.md0git fetch --all --prune && wt step for-each -- sh -c ' git rev-parse --verify -q @{u} >/dev/null || exit 0 g=$(git rev-pSTRING
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-pSTRING
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/content/extending.md0if git diff --quiet head && test -z "$(git ls-files --others --exclude-standard)"; then wt switch --create {{ to }} --exSTRING
HIGHdocs/static/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/content/extending.md0tail -f "$(wt config state logs --format=json | jq -r --arg name "{{ name | sanitize_hash }}" --arg kind "{{ kind }}" ' STRING
HIGHdocs/static/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/content/config.md0# <task>write a commit message for the staged changes below.</task> # # <format> # - subject line under 50 chars # - forSTRING
HIGHdocs/static/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/content/config.md0# <task>write a commit message for the combined effect of these commits.</task> # # <format> # - subject line under 50 cSTRING
HIGHdocs/static/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/content/config.md0# - explain the rationale in the body, not just the change #STRING
HIGHdocs/static/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/content/tips-patterns.md0wt config state vars set \ container='{{ repo }}-{{ branch | sanitize }}-postgres' \ port='{{ ('db-' ~ branch) | hash_poSTRING
HIGHdocs/static/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/content/tips-patterns.md0docker run -d --rm \ --name {{ vars.container }} \ -p {{ vars.port }}:5432 \ -e postgres_db={{ branch | sanitize_db }} \STRING
HIGHdocs/static/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/content/tips-patterns.md0f=$(mktemp); printf '\n\n' > "$f"; sed 's/^/# /' >> "$f"; ${editor:-vi} "$f" < /dev/tty > /dev/tty; grep -v '^#' "$f"STRING
HIGHdocs/static/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/content/worktrunk.md91- **[`wt list --full`](@/list.md#full-mode)** — [CI status](@/list.md#ci-status) and [AI-generated summaries](@/list.md#CODE
HIGHdocs/static/worktrunk.md76- **[`wt list --full`](https://worktrunk.dev/list/#full-mode)** — [CI status](https://worktrunk.dev/list/#ci-status) andCODE
HIGHdocs/static/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/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.rs870 // What the schema-2 envelope reports as requested — read from the taskCOMMENT
Verbosity Indicators31 hits · 51 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/switch.rs1823 // Step 2: From ping-pong worktree, switch back to mainCOMMENT
LOWtests/integration_tests/switch.rs1832 // Step 3: From main worktree, wt switch - should go to ping-pongCOMMENT
LOWtests/integration_tests/switch.rs1841 // Step 4: From ping-pong worktree, wt switch - should go back to mainCOMMENT
LOWtests/integration_tests/switch.rs1845 // Step 5: From main worktree, wt switch - should go to ping-pong again (ping-pong!)COMMENT
LOWtests/integration_tests/switch.rs6825 // Step 2: Switch to hist-feature again while already there (AlreadyAt)COMMENT
LOWtests/integration_tests/switch.rs6834 // Step 3: `wt switch -` should still go to main (the real previous),COMMENT
LOWtests/integration_tests/switch.rs1808 // Step 1: From main worktree, switch to ping-pong (creates worktree)COMMENT
LOWtests/integration_tests/switch.rs6813 // Step 1: Switch from main to hist-feature (establishes history: previous=main)COMMENT
LOWtests/integration_tests/list.rs116 // Step 1: From main, switch to feature (history: current=feature, previous=main)COMMENT
LOWtests/integration_tests/list.rs123 // Step 2: From feature, switch back to main (history: current=main, previous=feature)COMMENT
LOWtests/integration_tests/readme_sync.rs2658 // Step 0: Fill docs-example bodies in src/cli/mod.rs from snapshots. RunsSTRING
LOWtests/integration_tests/readme_sync.rs2664 // Step 1: Sync command pages (mod.rs → docs/content/*.md)STRING
LOWtests/integration_tests/readme_sync.rs2673 // Step 2: Sync standalone docs files (snapshots → docs/content/*.md).STRING
LOWtests/integration_tests/readme_sync.rs2696 // Step 3: Sync skill files (docs/content/*.md → skills/*)STRING
LOWtests/integration_tests/readme_sync.rs2705 // Step 4: Sync .well-known/agent-skills/ (skills/ → docs/static/)STRING
LOWtests/integration_tests/readme_sync.rs2709 // Step 5: Generate docs/static/llms.txt from docs/content front-matterSTRING
LOWtests/integration_tests/readme_sync.rs2713 // Step 6: Sync README from the now-fresh docs files. Runs last becauseSTRING
LOWtests/integration_tests/shell_wrapper.rs2856# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2863# Step 2: Get the completion function name (whatever it's called)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2871# Step 3: Set up completion environment and call the functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2881# Step 4: Verify we got completions (black-box: just check we got results)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2991# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs3000# Step 2: Test that COMPLETE mode works through our shell functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2894# Step 5: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/shell_wrapper.rs3022# 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.rs324 // Step 1: Filter out lock filesCOMMENT
LOWsrc/llm.rs356 // 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.rs1823 // Step 2: From ping-pong worktree, switch back to mainCOMMENT
LOWtests/integration_tests/switch.rs1832 // Step 3: From main worktree, wt switch - should go to ping-pongCOMMENT
LOWtests/integration_tests/switch.rs1841 // Step 4: From ping-pong worktree, wt switch - should go back to mainCOMMENT
LOWtests/integration_tests/switch.rs1845 // Step 5: From main worktree, wt switch - should go to ping-pong again (ping-pong!)COMMENT
LOWtests/integration_tests/switch.rs6825 // Step 2: Switch to hist-feature again while already there (AlreadyAt)COMMENT
LOWtests/integration_tests/switch.rs1808 // Step 1: From main worktree, switch to ping-pong (creates worktree)COMMENT
LOWtests/integration_tests/switch.rs6813 // Step 1: Switch from main to hist-feature (establishes history: previous=main)COMMENT
LOWtests/integration_tests/list.rs116 // Step 1: From main, switch to feature (history: current=feature, previous=main)COMMENT
LOWtests/integration_tests/list.rs123 // Step 2: From feature, switch back to main (history: current=main, previous=feature)COMMENT
LOWtests/integration_tests/list.rs1379/// NOTE: This function is used for doc generation. It removes fixture worktreesCOMMENT
LOWtests/integration_tests/readme_sync.rs2658 // Step 0: Fill docs-example bodies in src/cli/mod.rs from snapshots. RunsSTRING
LOWtests/integration_tests/readme_sync.rs2664 // Step 1: Sync command pages (mod.rs → docs/content/*.md)STRING
LOWtests/integration_tests/readme_sync.rs2673 // Step 2: Sync standalone docs files (snapshots → docs/content/*.md).STRING
LOWtests/integration_tests/readme_sync.rs2696 // Step 3: Sync skill files (docs/content/*.md → skills/*)STRING
LOWtests/integration_tests/readme_sync.rs2705 // Step 4: Sync .well-known/agent-skills/ (skills/ → docs/static/)STRING
LOWtests/integration_tests/readme_sync.rs2709 // Step 5: Generate docs/static/llms.txt from docs/content front-matterSTRING
LOWtests/integration_tests/readme_sync.rs2713 // Step 6: Sync README from the now-fresh docs files. Runs last becauseSTRING
LOWtests/integration_tests/shell_wrapper.rs2856# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2863# Step 2: Get the completion function name (whatever it's called)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2871# Step 3: Set up completion environment and call the functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2881# Step 4: Verify we got completions (black-box: just check we got results)COMMENT
LOWtests/integration_tests/shell_wrapper.rs2991# Step 1: Verify SOME completion is registered for 'wt' (black-box check)COMMENT
LOWtests/integration_tests/shell_wrapper.rs3000# Step 2: Test that COMPLETE mode works through our shell functionCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2894# Step 5: Verify expected subcommands are presentCOMMENT
LOWtests/integration_tests/shell_wrapper.rs3022# 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.rs324 // Step 1: Filter out lock filesCOMMENT
LOWsrc/llm.rs356 // 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 Imports31 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__.py37CODE
LOWdocs/demos/shared/__init__.py37CODE
LOWdocs/demos/shared/validation.py23CODE
AI Slop Vocabulary9 hits · 25 pts
SeverityFileLineSnippetContext
MEDIUMtests/integration_tests/switch_picker.rs3203 // gutter rather than the bare name is what makes the wait robust: under WindowsCOMMENT
MEDIUMtests/integration_tests/switch_picker_dry_run.rs48 // schema (not specific branches/modes) keeps the test robust to fixtureCOMMENT
MEDIUMtests/common/pty.rs50 // this is the more robust replacement.COMMENT
MEDIUMdocs/demos/shared/lib.py706 """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.yaml37 # Event workflows mark their own notifications read via the harnessCOMMENT
MEDIUMsrc/commands/process.rs689/// just makes its cleanup robust.COMMENT
MEDIUMsrc/commands/list/collect/mod.rs286//! ### Fundamentally uncacheableCOMMENT
MEDIUMsrc/commands/list/collect/mod.rs286//! ### Fundamentally uncacheableCOMMENT
Decorative Section Separators4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMtests/integration_tests/step_promote.rs386// ─── Swap tests ───────────────────────────────────────────────────────────COMMENT
MEDIUMdocs/demos/shared/lib.py969# =============================================================================COMMENT
MEDIUMdocs/demos/shared/lib.py971# =============================================================================COMMENT
MEDIUMsrc/git/repository/integration.rs979 /// └────── squash ── pad1 ── … ── padN = target (each pad reuses parent's tree)COMMENT
Self-Referential Comments4 hits · 10 pts
SeverityFileLineSnippetContext
MEDIUMTaskfile.yaml238 # Create the main repoCOMMENT
MEDIUMdocs/demos/shared/lib.py424 "# This file contains fish universal variable definitions.",STRING
MEDIUM.github/workflows/release.yaml264 # Create a GitHub Release while uploading all files to itCOMMENT
MEDIUMsrc/cli/mod.rs624## Creating a branchCOMMENT
Redundant / Tautological Comments5 hits · 8 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/shell_wrapper.rs1893 # Check if wt completion is registered and write result to marker fileCOMMENT
LOWtests/integration_tests/shell_wrapper.rs1944 # Check if wt completions are registered and write result to marker fileCOMMENT
LOWtests/integration_tests/shell_wrapper.rs2001 # Check if wt wrapper function is defined and write result to marker fileCOMMENT
LOWdocs/demos/shared/lib.py1112 # Check if Enter follows (possibly with Sleep in between)COMMENT
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.py696 set -l branch (git rev-parse --abbrev-ref HEAD 2>/dev/null)CODE
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml184# scaffolding; `registry` composes layers. Pinned to ≥ 0.3.17: that's whenCOMMENT
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/shell_wrapper.rs2557def test_login_invalid_password():CODE
LOWdocs/demos/shared/lib.py1068def extract_commands_from_tape(CODE
LOWdocs/demos/shared/validation.py234def validate_tui_demo_verbose(demo_name: str, gif_path: Path) -> tuple[bool, str]:CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtests/integration_tests/step_promote.rs318 .run_command(&["config", "user.email", "test@test.com"])CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/demos/shared/lib.py1068CODE
Modern Structural Boilerplate1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/demos/shared/__init__.py39__all__ = [CODE