Repository Analysis

entireio/cli

📜 Entire CLI hooks into your Git workflow to capture AI agent sessions as you work. Sessions are indexed alongside commits, creating a searchable record of how code was written in your repo.

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of entireio/cli, a Go project with 4,759 GitHub stars. SynthScan v2.0 examined 435,984 lines of code across 1276 source files, recording 901 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 2.4 places this repository in the Likely human-written 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).

2.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
4.8K
Stars
Go
Language
436.0K
Lines of Code
1.3K
Files
901
Pattern Hits
2026-07-14
Scan Date
0.00
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 5MEDIUM 26LOW 870

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 901 distinct pattern matches across 10 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 Block493 hits · 492 pts
SeverityFileLineSnippetContext
LOW.goreleaser.nonprod.yaml1# yaml-language-server: $schema=https://goreleaser.com/static/schema.jsonCOMMENT
LOWcmd/git-remote-entire/jurisdictionauth.go1package mainCOMMENT
LOWcmd/git-remote-entire/jurisdictionauth.go41// authenticates every git request: one token covers every repo the accountCOMMENT
LOWcmd/git-remote-entire/main.go1// Command git-remote-entire is the git remote helper for entire:// URLs.COMMENT
LOWcmd/git-remote-entire/main.go181// wrongClusterRe extracts the host that actually serves the repo from theCOMMENT
LOWcmd/git-remote-entire/main.go301// jurisdiction access token; they differ in what session credential seedsCOMMENT
LOWcmd/git-remote-entire/main.go361// resolveEnvTokenCreds builds the jurisdiction-token source for theCOMMENT
LOWcmd/entire/main.go61COMMENT
LOWcmd/entire/main.go101 //COMMENT
LOWcmd/entire/main.go141// The recorded signal lives in the shared procsignal package, written by theCOMMENT
LOWcmd/entire/cli/resolveref.go21// lists everything and filters client-side.COMMENT
LOWcmd/entire/cli/resolveref.go101 }COMMENT
LOWcmd/entire/cli/setup_github.go21COMMENT
LOWcmd/entire/cli/setup_github.go41 // user can commit themselves. The GitHub repo (if requested) isCOMMENT
LOWcmd/entire/cli/setup_github.go81// mode and non-TTY captures.COMMENT
LOWcmd/entire/cli/setup_github.go341func ghFlagsProvided(opts GitHubBootstrapOptions) bool {COMMENT
LOWcmd/entire/cli/setup_github.go941 }COMMENT
LOWcmd/entire/cli/repo_mirror_collaborators.go21 handle = "-"COMMENT
LOWcmd/entire/cli/repo_clone.go21// leading slash. owner/repo reuse the GitHub identifier charsets fromCOMMENT
LOWcmd/entire/cli/sessions.go21 "github.com/entireio/cli/cmd/entire/cli/session"COMMENT
LOWcmd/entire/cli/sessions.go41// (agent mid-write) is silently dropped so consumers never see aCOMMENT
LOWcmd/entire/cli/logout.go161COMMENT
LOWcmd/entire/cli/auth.go61//COMMENT
LOWcmd/entire/cli/auth.go261type contextsProvider func() ([]*contexts.Context, string, error)COMMENT
LOWcmd/entire/cli/auth.go301// is the bearer; fail-closed (a blank or malformed value errors, never fallsCOMMENT
LOWcmd/entire/cli/repo_mirror_test.go861COMMENT
LOWcmd/entire/cli/cell_target.go21// An interface (with a swappable constructor) so the resolver is unit-testableCOMMENT
LOWcmd/entire/cli/cell_target.go41// and the auth-layer client falls back to home-jurisdiction routing. ThatCOMMENT
LOWcmd/entire/cli/activity_cmd_test.go21// TestRunActivity_SilencesContextCanceled pins the codebase conventionCOMMENT
LOWcmd/entire/cli/entireapi_client.go21COMMENT
LOWcmd/entire/cli/repo_mirror_create_wizard.go141 return outCOMMENT
LOWcmd/entire/cli/attach.go41type attachOptions struct {COMMENT
LOWcmd/entire/cli/attach.go501// session data on push.COMMENT
LOWcmd/entire/cli/hook_registry.go101// When initLogging is true, it initializes and cleans up hook logging (used by the RunE fallbackCOMMENT
LOWcmd/entire/cli/cell_fanout.go21// let the caller merge. That mirrors the entire.io BFF's fan-outCOMMENT
LOWcmd/entire/cli/cell_fanout.go41 // baseURL is the cell's resolved apiUrl (resolveCellBaseURLs). Empty meansCOMMENT
LOWcmd/entire/cli/plugin.go181 // home dir, or a relative ENTIRE_PLUGIN_DIR override). The plugin nameCOMMENT
LOWcmd/entire/cli/repo_mirror.go41COMMENT
LOWcmd/entire/cli/repo_mirror.go201// owner may mirror it). No clone URL column: an un-onboarded repo doesn'tCOMMENT
LOWcmd/entire/cli/repo_mirror.go341 return runCoreForCluster(cmd, clusterHost, func(ctx context.Context, c *coreapi.Client) error {COMMENT
LOWcmd/entire/cli/repo_mirror.go381 return cmdCOMMENT
LOWcmd/entire/cli/agent_help_cmd.go21// advertised to agents when trails are enabled for the repo. While the trailsCOMMENT
LOWcmd/entire/cli/hook_guard.go1// hook_guard.go protects against cross-agent hook forwarding. Cursor IDECOMMENT
LOWcmd/entire/cli/repo.go61// its resolved cluster host and path — the form `git clone` andCOMMENT
LOWcmd/entire/cli/review_context.go141 return "Checkpoint context from commits in scope:\n" +COMMENT
LOWcmd/entire/cli/review_context.go161// the existing reviewPromptText helper to match the committed-pipeline fallbackCOMMENT
LOWcmd/entire/cli/git_operations.go361const metadataFetchDepth = 1_000_000_000COMMENT
LOWcmd/entire/cli/lifecycle.go201COMMENT
LOWcmd/entire/cli/lifecycle.go281// agentHelpBannerSuffix returns the SessionStart banner suffix that points anCOMMENT
LOWcmd/entire/cli/lifecycle.go581COMMENT
LOWcmd/entire/cli/lifecycle.go1021 slog.String("error", err.Error()))COMMENT
LOWcmd/entire/cli/lifecycle.go1401// tryAdoptEnv runs the shared env-adoption protocol for a launched-agentCOMMENT
LOWcmd/entire/cli/lifecycle.go1481// ENTIRE_INVESTIGATE_* env vars are present on the current process.COMMENT
LOWcmd/entire/cli/mcp.go21// counterpart to the passive `entire status` / `entire help` discovery path: theCOMMENT
LOWcmd/entire/cli/repo_mirror_probe.go21//COMMENT
LOWcmd/entire/cli/repo_mirror_probe.go61 return owner, repo, nilCOMMENT
LOWcmd/entire/cli/repo_mirror_probe.go101// it reaches a terminal status or the deadline/cancellation fires. It returnsCOMMENT
LOWcmd/entire/cli/attribution.go481 }COMMENT
LOWcmd/entire/cli/attribution.go501 // print a misleading caveat (common for older metadata and attach/trailCOMMENT
LOWcmd/entire/cli/setup.go1481 Value(&selected),COMMENT
433 more matches not shown…
Fake / Example Data262 hits · 236 pts
SeverityFileLineSnippetContext
LOWcmd/entire/cli/reset_test.go47 sig := object.Signature{Name: "test", Email: "test@test.com"}CODE
LOWcmd/entire/cli/hook_registry_test.go42 gitConfig := exec.CommandContext(context.Background(), "git", "config", "user.email", "test@test.com")CODE
LOWcmd/entire/cli/hook_registry_test.go646 gitConfig := exec.CommandContext(context.Background(), "git", "config", "user.email", "test@test.com")CODE
LOWcmd/entire/cli/status_test.go74 Email: "test@test.com",CODE
LOWcmd/entire/cli/explain_test.go1032 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/explain_test.go3456 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/explain_test.go3493 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/explain_test.go3514 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/explain_test.go3584 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/explain_test.go3617 AuthorEmail: "test@test.com", IsFirstCheckpoint: true,CODE
LOWcmd/entire/cli/explain_test.go3629 AuthorEmail: "test@test.com", IsFirstCheckpoint: false,CODE
LOWcmd/entire/cli/explain_test.go4074 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/explain_test.go4122 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/explain_test.go4242 {"config", "user.email", "test@test.com"},CODE
LOWcmd/entire/cli/doctor_test.go53 Author: object.Signature{Name: "test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/doctor_test.go54 Committer: object.Signature{Name: "test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/doctor_test.go327 Author: object.Signature{Name: "test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/doctor_test.go328 Committer: object.Signature{Name: "test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/clean_test.go58 sig := object.Signature{Name: "test", Email: "test@test.com"}CODE
LOWcmd/entire/cli/lifecycle_test.go1087 Email: "test@test.com",CODE
LOWcmd/entire/cli/rewind_imports_test.go35 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/migrate_test.go39 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/migrate_test.go80 commitHash, err := CreateCommit(ctx, repo, newTree, ref.Hash(), "test: legacy metadata", "Test", "test@test.com")CODE
LOWcmd/entire/cli/checkpoint/migrate_test.go381 advanced, err := CreateCommit(ctx, repo, headCommit.TreeHash, imported, "refs-store write", "Test", "test@test.com")CODE
LOWcmd/entire/cli/checkpoint/persistent_signing_test.go61 Email: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/persistent_imported_test.go34 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOW…entire/cli/checkpoint/persistent_phantom_paths_test.go35 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOW…entire/cli/checkpoint/persistent_phantom_paths_test.go49 AuthorEmail: "test@test.com",CODE
LOW…entire/cli/checkpoint/persistent_phantom_paths_test.go81 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOW…entire/cli/checkpoint/persistent_phantom_paths_test.go95 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go132 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go324 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go361 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go383 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go410 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go448 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go552 commitHash, err := CreateCommit(context.Background(), store.repo, treeHash, plumbing.ZeroHash, "Initialize metadata braCODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go567 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go872 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go886 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go1776 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go1814 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go1912 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go1942 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2007 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2045 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2119 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2160 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2237 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2277 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2378 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2399 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2498 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2517 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2609 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2628 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2691 Author: &object.Signature{Name: "Test", Email: "test@test.com"},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2733 AuthorEmail: "test@test.com",CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2813 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
LOWcmd/entire/cli/checkpoint/checkpoint_test.go2849 AuthorEmail: "test@test.com",CODE
202 more matches not shown…
Structural Annotation Overuse76 hits · 133 pts
SeverityFileLineSnippetContext
LOWcmd/entire/cli/setup_github.go149 // Step 1: confirm we should git init here.COMMENT
LOWcmd/entire/cli/setup_github.go158 // Step 2: git init.COMMENT
LOWcmd/entire/cli/setup_github.go168 // Step 3: decide whether to create a GitHub repo. Creating a remote is anCOMMENT
LOWcmd/entire/cli/setup_github.go200 // Step 4: collect GitHub repo details up front so all prompts areCOMMENT
LOWcmd/entire/cli/setup_github.go212 // Step 5: resolve commit message (+ skip decision) and ensure gitCOMMENT
LOWcmd/entire/cli/setup_github.go229 // Step 6: pushing is also an explicit opt-in, separate from creating theCOMMENT
LOWcmd/entire/cli/search_cmd.go514 // Step 1: Get repos index from the control plane.COMMENT
LOWcmd/entire/cli/search_cmd.go537 // Step 2: Resolve repo slug filters to ULIDs and narrow to matching cells.COMMENT
LOWcmd/entire/cli/search_cmd.go552 // Step 3: Group repos by cell and resolve baseURLs via shared helpers.COMMENT
LOWcmd/entire/cli/search_cmd.go559 // Step 4: Fan out via the shared fanOutCells helper.COMMENT
LOWcmd/entire/cli/trail_cmd.go1511 // Step 1: Title and bodyCOMMENT
LOWcmd/entire/cli/trail_cmd.go1559 // Step 2: Branch (derived from title) and statusCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go47 // Step 1: PreTask - creates pre-task fileCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go59 // Step 2: PostTodo - simulate TodoWrite calls with file changes between themCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go110 // Step 3: PostTask - creates final task checkpointCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go292 // Step 2: Overwrite hooks with third-party content (simulating lefthook, husky, etc.)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go301 // Step 3: Verify hooks are no longer Entire hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go306 // Step 4: Second user-prompt-submit should reinstall hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go312 // Step 5: Verify hooks are reinstalledCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go317 // Step 6: Verify the hooks chain to original hooks (backup should exist)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go346 // Step 2: Delete all hooks (simulating aggressive third-party tool)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go354 // Step 3: Verify hooks are goneCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go359 // Step 4: Second user-prompt-submit should reinstall hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go365 // Step 5: Verify hooks are reinstalledCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go280 // Step 1: First user-prompt-submit installs hooks via EnsureSetupCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go334 // Step 1: First user-prompt-submit installs hooks via EnsureSetupCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go101 // Step 1: User adds 5 lines to the fileCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go107 // Step 2: User stages these 5 linesCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go112 // Step 3: User adds 5 MORE lines to worktree (unstaged)COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go108 // Step 1: extract images (before redaction).COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go123 // Step 2: redact the placeholder-bearing transcript.COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go142 // Step 3: reinject restores the exact image bytes.COMMENT
LOW.claude/skills/changelog/SKILL.md19## Step 1: Gather DataCOMMENT
LOW.claude/skills/changelog/SKILL.md26## Step 2: Identify External ContributorsCOMMENT
LOW.claude/skills/changelog/SKILL.md38## Step 3: Write the EntryCOMMENT
LOW.claude/skills/e2e/implement.md21## Step 1: Identify FixesCOMMENT
LOW.claude/skills/e2e/implement.md55## Step 2: Ask the UserCOMMENT
LOW.claude/skills/e2e/implement.md65## Step 3: Apply FixesCOMMENT
LOW.claude/skills/e2e/implement.md108## Step 4: SummaryCOMMENT
LOW.claude/skills/e2e/triage-ci.md56### Step 1: Analyze Each FailureCOMMENT
LOW.claude/skills/e2e/triage-ci.md64### Step 2: Classify Each FailureCOMMENT
LOW.claude/skills/e2e/triage-ci.md119### Step 3: Cross-Agent CorrelationCOMMENT
LOW.claude/skills/e2e/triage-ci.md126### Step 4: Present Findings ReportCOMMENT
LOW.claude/skills/e2e/triage-ci.md167### Step 5: SummaryCOMMENT
LOW.claude/skills/agent-integration/test-writer.md12### Step 1: Read E2E Test InfrastructureCOMMENT
LOW.claude/skills/agent-integration/test-writer.md27### Step 2: Read Existing E2E Test ScenariosCOMMENT
LOW.claude/skills/agent-integration/test-writer.md35### Step 3: Read Checkpoint Scenarios DocCOMMENT
LOW.claude/skills/agent-integration/test-writer.md39### Step 4: Create Agent ImplementationCOMMENT
LOW.claude/skills/agent-integration/test-writer.md163### Step 5: Update SetupRepo (if needed)COMMENT
LOW.claude/skills/agent-integration/test-writer.md173### Step 6: VerifyCOMMENT
LOW.claude/skills/agent-integration/test-writer.md183### Step 7: CommitCOMMENT
LOW.claude/skills/agent-integration/implementer.md25### Step 1: Read Implementation GuideCOMMENT
LOW.claude/skills/agent-integration/implementer.md34### Step 2: Read Reference ImplementationCOMMENT
LOW.claude/skills/agent-integration/implementer.md40### Step 3: Create Bare-Minimum Compiling PackageCOMMENT
LOW.claude/skills/agent-integration/implementer.md72### Step 4: E2E Tier 1 — `TestHumanOnlyChangesAndCommits`COMMENT
LOW.claude/skills/agent-integration/implementer.md94### Step 5: E2E Tier 2 — `TestSingleSessionManualCommit`COMMENT
LOW.claude/skills/agent-integration/implementer.md116### Step 6: E2E Tier 2b — `TestCheckpointMetadataDeepValidation`COMMENT
LOW.claude/skills/agent-integration/implementer.md137### Step 7: E2E Tier 3 — `TestSingleSessionAgentCommitInTurn`COMMENT
LOW.claude/skills/agent-integration/implementer.md156### Step 8: E2E Tier 4 — Multi-Session TestsCOMMENT
LOW.claude/skills/agent-integration/implementer.md177### Step 9: E2E Tier 5 — File Operation Edge CasesCOMMENT
16 more matches not shown…
Verbosity Indicators32 hits · 60 pts
SeverityFileLineSnippetContext
LOWcmd/entire/cli/setup_github.go149 // Step 1: confirm we should git init here.COMMENT
LOWcmd/entire/cli/setup_github.go158 // Step 2: git init.COMMENT
LOWcmd/entire/cli/setup_github.go168 // Step 3: decide whether to create a GitHub repo. Creating a remote is anCOMMENT
LOWcmd/entire/cli/setup_github.go200 // Step 4: collect GitHub repo details up front so all prompts areCOMMENT
LOWcmd/entire/cli/setup_github.go212 // Step 5: resolve commit message (+ skip decision) and ensure gitCOMMENT
LOWcmd/entire/cli/setup_github.go229 // Step 6: pushing is also an explicit opt-in, separate from creating theCOMMENT
LOWcmd/entire/cli/search_cmd.go514 // Step 1: Get repos index from the control plane.COMMENT
LOWcmd/entire/cli/search_cmd.go537 // Step 2: Resolve repo slug filters to ULIDs and narrow to matching cells.COMMENT
LOWcmd/entire/cli/search_cmd.go552 // Step 3: Group repos by cell and resolve baseURLs via shared helpers.COMMENT
LOWcmd/entire/cli/search_cmd.go559 // Step 4: Fan out via the shared fanOutCells helper.COMMENT
LOWcmd/entire/cli/trail_cmd.go1511 // Step 1: Title and bodyCOMMENT
LOWcmd/entire/cli/trail_cmd.go1559 // Step 2: Branch (derived from title) and statusCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go47 // Step 1: PreTask - creates pre-task fileCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go59 // Step 2: PostTodo - simulate TodoWrite calls with file changes between themCOMMENT
LOW…tire/cli/integration_test/subagent_checkpoints_test.go110 // Step 3: PostTask - creates final task checkpointCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go292 // Step 2: Overwrite hooks with third-party content (simulating lefthook, husky, etc.)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go301 // Step 3: Verify hooks are no longer Entire hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go306 // Step 4: Second user-prompt-submit should reinstall hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go312 // Step 5: Verify hooks are reinstalledCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go317 // Step 6: Verify the hooks chain to original hooks (backup should exist)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go346 // Step 2: Delete all hooks (simulating aggressive third-party tool)COMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go354 // Step 3: Verify hooks are goneCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go359 // Step 4: Second user-prompt-submit should reinstall hooksCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go365 // Step 5: Verify hooks are reinstalledCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go280 // Step 1: First user-prompt-submit installs hooks via EnsureSetupCOMMENT
LOWcmd/entire/cli/integration_test/hooks_test.go334 // Step 1: First user-prompt-submit installs hooks via EnsureSetupCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go101 // Step 1: User adds 5 lines to the fileCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go107 // Step 2: User stages these 5 linesCOMMENT
LOWcmd/entire/cli/strategy/manual_commit_staging_test.go112 // Step 3: User adds 5 MORE lines to worktree (unstaged)COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go108 // Step 1: extract images (before redaction).COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go123 // Step 2: redact the placeholder-bearing transcript.COMMENT
LOWcmd/entire/cli/strategy/condense_images_test.go142 // Step 3: reinject restores the exact image bytes.COMMENT
Modern AI Meta-Vocabulary13 hits · 44 pts
SeverityFileLineSnippetContext
MEDIUMcmd/entire/cli/runner_init.go81// the re-run case where there is nothing to scaffold.COMMENT
MEDIUMcmd/entire/cli/setup_managed_scaffold.go16// managedScaffoldStatus is the outcome of writing an Entire-managed scaffold fileCOMMENT
MEDIUMcmd/entire/cli/setup_agent_help_skill_test.go80 // Idempotent: a second scaffold of identical content reports unchanged.COMMENT
MEDIUMcmd/entire/cli/investigate/cmd.go879// scaffold. The seed-doc path takes precedence (Bootstrap re-derives fromCOMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go38// 1. The first `# Investigation: <topic>` line — the scaffold's own titleCOMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go38// 1. The first `# Investigation: <topic>` line — the scaffold's own titleCOMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go65// the scaffold and embed the seed bytes under theCOMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go70// the scaffold with the topic printed under `## Question`.COMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go73// scaffold and embed those bytes under `## Question`,COMMENT
MEDIUMcmd/entire/cli/investigate/bootstrap.go179// renderInvestigationScaffold returns the investigation scaffold body.COMMENT
MEDIUMcmd/entire/cli/investigate/cmd_test.go270 // and the scaffold's `# Investigation:` header is a stable anchor).COMMENT
MEDIUMcmd/entire/cli/investigate/prompt.go43 // rendered prompt. Lets users inject project-specific guardrails intoCOMMENT
MEDIUMcmd/entire/cli/runnerdefaults/embed.go2// `entire runner setup` can scaffold them into a repository that has none yet.COMMENT
Synthetic Comment Markers5 hits · 38 pts
SeverityFileLineSnippetContext
HIGHcmd/entire/cli/explain_test.go2615 // Should show AI-generated intent and outcome as markdown.COMMENT
HIGHcmd/entire/cli/activity_types.go110// (custom name > AI-generated name > heuristic). repo_full_name / is_privateCOMMENT
HIGHapi/checkpoint/metadata.go141 // Summary is an optional AI-generated summary for this checkpoint.COMMENT
HIGHapi/checkpoint/metadata.go383 // AI-generated summary of the checkpointCOMMENT
HIGHapi/checkpoint/metadata.go518// Summary contains AI-generated summary of a checkpoint.COMMENT
Decorative Section Separators7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMcmd/entire/cli/status_style.go262// sectionRule renders a section header like: ── Active Sessions ────────────COMMENT
MEDIUMcmd/entire/cli/search_tui.go672// ─── View ────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcmd/entire/cli/search_tui.go1613// ─── Column Layout ───────────────────────────────────────────────────────────COMMENT
MEDIUMcmd/entire/cli/search_tui.go1662// ─── Formatting Helpers ──────────────────────────────────────────────────────COMMENT
MEDIUMcmd/entire/cli/search_tui.go1694// ─── Snippet Markdown ────────────────────────────────────────────────────────COMMENT
MEDIUMcmd/entire/cli/search_tui.go1783// ─── Static Fallback ─────────────────────────────────────────────────────────COMMENT
MEDIUMcmd/entire/cli/review/tui_detail.go75// 1. Header line: "─── <name> (<n> events) ─────────────" (filled to termWidth)COMMENT
AI Slop Vocabulary5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUMcmd/entire/cli/checkpoint/id/id.go123// robust for legacy and ULID IDs alike and impossible to compute inconsistentlyCOMMENT
MEDIUMcmd/entire/cli/strategy/hooks.go102// It delegates to `git rev-parse --git-dir` to leverage git's own validation.COMMENT
MEDIUM.claude/skills/test-repo/test-harness.sh2# Test harness for Entire CLI strategy testingCOMMENT
MEDIUM.claude/skills/test-repo/test-harness.sh3# Usage: test-harness.sh <step> [args...]COMMENT
MEDIUMe2e/testutil/repo.go827// or index is non-empty. This keeps cloned-repo E2E tests robust whenCOMMENT
Redundant / Tautological Comments7 hits · 10 pts
SeverityFileLineSnippetContext
LOWscripts/install.sh272 # Check if the installed binary is the one that will be found in PATHCOMMENT
LOWscripts/migrate-sessions.sh208# Check if a checkpoint is up-to-date on target branch (same source commit)COMMENT
LOWscripts/migrate-sessions.sh219 # Check if metadata.json exists on targetCOMMENT
LOWscripts/migrate-sessions.sh224 # Check if same source commit (up-to-date)COMMENT
LOWscripts/migrate-sessions.sh252 # Check if this is session metadata (has session_id) or already aggregatedCOMMENT
LOWscripts/migrate-sessions.sh473 # Check if already up-to-dateCOMMENT
LOWscripts/migrate-sessions.sh596 # Check if any of the modified checkpoints need migrationCOMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.gemini/test-hooks.sh12# Create a temp directory for test transcriptCOMMENT