Repository Analysis

cobusgreyling/loop-engineering

Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.

3.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of cobusgreyling/loop-engineering, a JavaScript project with 7,747 GitHub stars. SynthScan v2.0 examined 24,109 lines of code across 357 source files, recording 31 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 3.5 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).

3.5
Adjusted Score
3.5
Raw Score
100%
Time Factor
2026-07-14
Last Push
7.7K
Stars
JavaScript
Language
24.1K
Lines of Code
357
Files
31
Pattern Hits
2026-07-14
Scan Date
0.02
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 6MEDIUM 18LOW 7

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 31 distinct pattern matches across 7 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.

Cross-File Repetition6 hits · 30 pts
SeverityFileLineSnippetContext
HIGHstarters/minimal-loop-codex/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/ci-sweeper/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/pr-babysitter/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/issue-triage/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/post-merge-cleanup/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
HIGHstarters/dependency-sweeper/.codex/agents/verifier.toml0you are the checker in a maker/checker split. default stance: reject until proven otherwise. checklist (all must pass foSTRING
Decorative Section Separators10 hits · 29 pts
SeverityFileLineSnippetContext
MEDIUMtools/mcp-server/src/index.ts26// ── Resources ──────────────────────────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts113// ── Resource Templates (dynamic) ───────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts169// ── Tools ──────────────────────────────────────────────────────────COMMENT
MEDIUMtools/mcp-server/src/index.ts429// ── Start ──────────────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts76// ── Error normalization ────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts99// ── Circuit breaker ────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts212// ── Pruning ────────────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts259// ── Summarization ──────────────────────────────────────────────────COMMENT
MEDIUMtools/loop-context/src/context-manager.ts313// ── Injection ──────────────────────────────────────────────────────COMMENT
MEDIUM…ources/ky-cut-surface-philosophy-v0_1/TERMINAL_ART.txt1┌──[ KUNST-TERMINALEN // KY CUT SURFACE v0.1 ]──────────────────────────────┐CODE
Modern AI Meta-Vocabulary6 hits · 13 pts
SeverityFileLineSnippetContext
MEDIUMtools/loop-audit/src/cli.ts90 console.log(' # Or scaffold automatically:');CODE
MEDIUMtools/loop-audit/src/cli.ts94 console.log(' # IMPORTANT (v1.4): After scaffolding, actually RUN a loop (report-only) and commit the updated STATECODE
MEDIUMdocs/QUICKSTART.md13Not sure which loop? Use the [interactive pattern picker](https://cobusgreyling.github.io/loop-engineering/#interactive)CODE
MEDIUMdocs/QUICKSTART.md13Not sure which loop? Use the [interactive pattern picker](https://cobusgreyling.github.io/loop-engineering/#interactive)CODE
MEDIUMexamples/codex/issue-triage.md36Install `issue-triage` per [Codex Agent Skills](https://developers.openai.com/codex/skills) — scaffold with `loop-init` CODE
MEDIUMexamples/github-actions/ci-sweeper.yml1# CI Sweeper — event-driven on workflow failureCOMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMexamples/github-actions/daily-triage.yml2# Invokes your agent harness with a triage prompt. Adapt the "Run agent" stepCOMMENT
MEDIUMexamples/github-actions/issue-triage.yml3# issue-triage-state.md. Wire the "Run triage agent" step to your harness.COMMENT
Unused Imports4 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/generate-star-history.py11CODE
LOWscripts/generate-star-history.py13CODE
LOWscripts/generate-audit-demo-gif.py4CODE
LOWscripts/generate-audit-demo-gif.py7CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWtools/loop-context/src/budget-resolver.ts13export function assertValidBudgetScenario(scenario: string): asserts scenario is BudgetScenario {CODE
LOWtools/loop-context/src/budget-resolver.ts70export async function resolveTokenBudgetFromPattern(input: BudgetFromPatternInput): Promise<number> {CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWstories/README.md21COMMENT