3.2

Adjusted Signal

3.2

Raw Pattern Score

100%

Time Factor

2026-10-19

Last Push

30.8K

Stars

Shell

Language

123.6K

Lines of Code

628

Files

311

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 13.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 294 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 1 finding(s).

Agent Over-Engineering Ratio 1.8/100 · LOW

Are wrappers, guards, and repeated structures necessary? 16 finding(s).

PR Review Velocity Impact 14.0/100 · LOW

Which changes need focused human review? 311 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 31LOW 280

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 311 distinct pattern matches across 9 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block231 hits · 224 pts

Severity	File	Line	Snippet	Context
LOW	project.yaml	1	# CCGS project configuration — single source of truth for project settings.	COMMENT
LOW	project.yaml	21	# and saves would stop changing anything. `/start` states the same rule for the	COMMENT
LOW	design/registry/entities.yaml	1	# Game World Entity Registry	COMMENT
LOW	design/registry/entities.yaml	21	# after asking)	COMMENT
LOW	design/registry/entities.yaml	41	# path; referenced_by.*inventory never matches)	COMMENT
LOW	design/registry/entities.yaml	61	# Register an entity here when it appears in more than one GDD — e.g., an	COMMENT
LOW	design/registry/entities.yaml	81	# drops:	COMMENT
LOW	design/registry/entities.yaml	101	# items:	COMMENT
LOW	design/registry/entities.yaml	121	#	COMMENT
LOW	design/registry/entities.yaml	141	# - crit_multiplier	COMMENT
LOW	design/registry/entities.yaml	161	# Example:	COMMENT
LOW	design/registry/entities.yaml	181	# - design/gdd/progression.md # progression unlocks additional slots	COMMENT
LOW	.claude/statusline.sh	1	#!/usr/bin/env bash	COMMENT
LOW	.claude/statusline.sh	161	fi	COMMENT
LOW	.claude/docs/workflow-catalog.yaml	1	# Workflow Catalog	COMMENT
LOW	.claude/hooks/validate-write.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/validate-write.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/validate-write.sh	41	# step, because hooks do not run in every tool.	COMMENT
LOW	.claude/hooks/validate-read.sh	21	# features.read_guard_kb (40 KB); features.read_guard: off turns it off.	COMMENT
LOW	.claude/hooks/validate-push.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/validate-push.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/validate-push.sh	41	#	COMMENT
LOW	.claude/hooks/validate-skill-change.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/validate-skill-change.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/validate-skill-change.sh	41		COMMENT
LOW	.claude/hooks/detect-gaps.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/detect-gaps.sh	61	# Check if a design record exists.	COMMENT
LOW	.claude/hooks/detect-gaps.sh	81	# `Source/`. Testing only `src/` meant a Unity project with a full codebase	COMMENT
LOW	.claude/hooks/detect-gaps.sh	161	fi	COMMENT
LOW	.claude/hooks/detect-gaps.sh	301	echo "⚠️ GAP: Large codebase ($SRC_FILES files) but no production planning found"	COMMENT
LOW	.claude/hooks/session-stop.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/session-stop.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/session-stop.sh	61	# APPEND ONLY WHEN THE CONTENT CHANGED.	COMMENT
LOW	.claude/hooks/pre-compact.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/pre-compact.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/validate-agent-artifact.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/validate-agent-artifact.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/validate-agent-artifact.sh	41	# from its prompt only: the transcript's first user message. The rest of the	COMMENT
LOW	.claude/hooks/log-agent-stop.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/log-agent-stop.sh	21	# overriding a caller that legitimately means somewhere else.	COMMENT
LOW	.claude/hooks/update-check.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/update-check.sh	21	# Cross-platform: Windows Git Bash, macOS bash 3.2, Linux. Needs curl or wget	COMMENT
LOW	.claude/hooks/validate-commit.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/validate-commit.sh	41		COMMENT
LOW	.claude/hooks/validate-commit.sh	61	# starting t or n became a tab or a line break), the -C check below found	COMMENT
LOW	.claude/hooks/validate-commit.sh	81	# `C:\Git\cmd\git.exe`) are allowed, and a QUOTED path to git ("C:\Program	COMMENT
LOW	.claude/hooks/validate-commit.sh	101	# next before any of this runs, so `git \` then `commit` on the next line is	COMMENT
LOW	.claude/hooks/validate-commit.sh	181		COMMENT
LOW	.claude/hooks/validate-commit.sh	241	WT_FILES=$($_GIT diff --name-only 2>/dev/null)	COMMENT
LOW	.claude/hooks/validate-commit.sh	261	# A relative pathspec resolves where the commit runs, and this hook runs at the	COMMENT
LOW	.claude/hooks/validate-commit.sh	441	fi	COMMENT
LOW	.claude/hooks/validate-commit.sh	461	# scan announces that it did not run instead of skipping in silence.	COMMENT
LOW	.claude/hooks/validate-commit.sh	481	# Two independent fixes, because either alone is a mitigation rather than a	COMMENT
LOW	.claude/hooks/validate-commit.sh	601	# `standard`, and no GDD requirement at all at `minimal`. A jam project on the	COMMENT
LOW	.claude/hooks/validate-commit.sh	641		COMMENT
LOW	.claude/hooks/validate-commit.sh	721	WARNINGS="$WARNINGS\nSKIPPED: no writable scratch location, so the GDD section check did NOT run on the stag	COMMENT
LOW	.claude/hooks/validate-commit.sh	741	#	COMMENT
LOW	.claude/hooks/log-instructions.sh	1	#!/bin/bash	COMMENT
LOW	.claude/hooks/log-instructions.sh	21	#	COMMENT
LOW	.claude/hooks/log-instructions.sh	41	# this hook the only way to get it was to infer it from behaviour afterwards.	COMMENT
171 more matches not shown…

Structural Annotation Overuse38 hits · 65 pts

Severity	File	Line	Snippet	Context
LOW⚡	.claude/docs/hooks-reference/pre-push-test-gate.md	33	# Step 1: Build	COMMENT
LOW⚡	.claude/docs/hooks-reference/pre-push-test-gate.md	41	# Step 2: Unit tests	COMMENT
LOW⚡	.claude/docs/hooks-reference/pre-push-test-gate.md	50	# Step 3: Integration tests (only for protected branches)	COMMENT
LOW⚡	.claude/docs/hooks-reference/pre-push-test-gate.md	55	# Step 4: Smoke tests	COMMENT
LOW⚡	.claude/docs/hooks-reference/pre-push-test-gate.md	60	# Step 5: Performance regression check	COMMENT
LOW⚡	.claude/docs/templates/adoption-plan.md	13	## Step 1: Fix Blocking Gaps	COMMENT
LOW⚡	.claude/docs/templates/adoption-plan.md	19	## Step 2: Fix High-Priority Gaps	COMMENT
LOW⚡	.claude/docs/templates/adoption-plan.md	25	## Step 3: Bootstrap Infrastructure	COMMENT
LOW	.claude/docs/templates/adoption-plan.md	55	## Step 4: Medium-Priority Gaps	COMMENT
LOW	.claude/docs/templates/adoption-plan.md	61	## Step 5: Optional Improvements	COMMENT
LOW⚡	.claude/skills/adopt/references/6-write.md	28	## Step 1: Fix Blocking Gaps	COMMENT
LOW⚡	.claude/skills/adopt/references/6-write.md	34	## Step 2: Fix High-Priority Gaps	COMMENT
LOW⚡	.claude/skills/adopt/references/6-write.md	40	## Step 3: Bootstrap Infrastructure	COMMENT
LOW	.claude/skills/adopt/references/6-write.md	70	## Step 4: Medium-Priority Gaps	COMMENT
LOW	.claude/skills/adopt/references/6-write.md	76	## Step 5: Optional Improvements	COMMENT
LOW	.claude/skills/team-audio/SKILL.md	126	### Step 1: Audio Direction (audio-director)	COMMENT
LOW	.claude/skills/team-audio/SKILL.md	134	### Step 2: Sound Design and Audio Accessibility (parallel)	COMMENT
LOW	.claude/skills/team-audio/SKILL.md	155	### Step 3: Technical Implementation (parallel)	COMMENT
LOW	.claude/skills/team-audio/SKILL.md	171	### Step 4: Code Integration (gameplay-programmer)	COMMENT
LOW	.claude/skills/help/SKILL.md	33	## Step 1: Read the Catalog	COMMENT
LOW	.claude/skills/help/SKILL.md	64	## Step 2: Determine Current Phase	COMMENT
LOW	.claude/skills/help/SKILL.md	99	## Step 3: Read Session Context	COMMENT
LOW	.claude/skills/help/SKILL.md	118	## Step 4: Check Step Completion for the Current Phase	COMMENT
LOW	.claude/skills/help/SKILL.md	244	## Step 5: Find Position and Identify Next Steps	COMMENT
LOW	.claude/skills/help/SKILL.md	264	## Step 6: Check for In-Progress Work	COMMENT
LOW	.claude/skills/help/SKILL.md	272	## Step 7: Present Output	COMMENT
LOW	.claude/skills/help/SKILL.md	334	## Step 8: Gate Warning (if close)	COMMENT
LOW	.claude/skills/help/SKILL.md	345	## Step 9: Escalation Paths	COMMENT
LOW	.claude/skills/team-level/SKILL.md	123	### Step 1: Narrative + Visual Direction (narrative-director + world-builder + art-director, parallel)	COMMENT
LOW	.claude/skills/team-level/SKILL.md	148	### Step 2: Layout and Encounter Design (level-designer)	COMMENT
LOW	.claude/skills/team-level/SKILL.md	173	### Step 3: Systems Integration (systems-designer)	COMMENT
LOW	.claude/skills/team-level/SKILL.md	183	### Step 4: Production Concepts + Accessibility (art-director + accessibility-specialist, parallel)	COMMENT
LOW	.claude/skills/team-level/SKILL.md	209	### Step 5: QA Planning (qa-tester)	COMMENT
LOW	docs/WORKFLOW-GUIDE.md	47	### Step 1: Clone and Open	COMMENT
LOW	docs/WORKFLOW-GUIDE.md	54	### Step 2: Run /start	COMMENT
LOW	docs/WORKFLOW-GUIDE.md	72	### Step 3: Verify Hooks Are Working	COMMENT
LOW	docs/WORKFLOW-GUIDE.md	88	### Step 4: Ask for Help Anytime	COMMENT
LOW	docs/WORKFLOW-GUIDE.md	102	### Step 5: Create Your Directory Structure	COMMENT

Decorative Section Separators15 hits · 45 pts

Severity	File	Line	Snippet	Context
MEDIUM	design/registry/entities.yaml	59	# ─── ENTITIES ────────────────────────────────────────────────────────────────	COMMENT
MEDIUM	design/registry/entities.yaml	89	# ─── ITEMS ───────────────────────────────────────────────────────────────────	COMMENT
MEDIUM	design/registry/entities.yaml	117	# ─── FORMULAS ────────────────────────────────────────────────────────────────	COMMENT
MEDIUM	design/registry/entities.yaml	151	# ─── CONSTANTS ───────────────────────────────────────────────────────────────	COMMENT
MEDIUM	.claude/hooks/validate-commit.sh	470	# ---------------------------------------------------------------------------	COMMENT
MEDIUM	.claude/hooks/validate-commit.sh	498	# ---------------------------------------------------------------------------	COMMENT
MEDIUM	.claude/hooks/yaml-helper.sh	217	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	.claude/hooks/yaml-helper.sh	219	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	.claude/hooks/yaml-helper.sh	1180	# =============================================================================	COMMENT
MEDIUM	.claude/hooks/yaml-helper.sh	1195	# =============================================================================	COMMENT
MEDIUM	docs/registry/architecture.yaml	45	# ─── STATE OWNERSHIP ─────────────────────────────────────────────────────────	COMMENT
MEDIUM	docs/registry/architecture.yaml	75	# ─── INTERFACE CONTRACTS ──────────────────────────────────────────────────────	COMMENT
MEDIUM	docs/registry/architecture.yaml	106	# ─── PERFORMANCE BUDGETS ──────────────────────────────────────────────────────	COMMENT
MEDIUM	docs/registry/architecture.yaml	136	# ─── API DECISIONS ───────────────────────────────────────────────────────────	COMMENT
MEDIUM	docs/registry/architecture.yaml	162	# ─── FORBIDDEN PATTERNS ──────────────────────────────────────────────────────	COMMENT

Modern AI Meta-Vocabulary13 hits · 38 pts

Severity	File	Line	Snippet	Context
MEDIUM	studio-tests/skills/utility/test-setup.md	163	### Case 5: Director Gate Check — No gate; test-setup is a scaffolding utility	COMMENT
MEDIUM	studio-tests/skills/utility/test-helpers.md	163	### Case 5: Director Gate Check — No gate; test-helpers is a scaffolding utility	COMMENT
MEDIUM	.claude/docs/run-and-observe.md	57	### Godot 4 — zero scaffold	COMMENT
MEDIUM	.claude/docs/effects-map.md	410	### Team orchestration skills (pipeline behavior — different relationship)	COMMENT
MEDIUM	.claude/docs/error-recovery-protocol.md	4	the `## Error Recovery Protocol` section of each orchestration and review skill.	CODE
MEDIUM	.claude/hooks/validate-agent-artifact.sh	34	# the file its return contract named. An orchestrating skill ends each agent	COMMENT
MEDIUM	.claude/scripts/write-guard.sh	196	# QA evidence folder. Other paths never ask test-scaffold.sh.	COMMENT
MEDIUM	.claude/scripts/write-guard.sh	200	# The files /test-setup creates, as test-scaffold.sh lists them per engine.	COMMENT
MEDIUM	.claude/scripts/test-scaffold.sh	2	# test-scaffold.sh — creates the files /test-setup scaffolds for one engine,	COMMENT
MEDIUM	.claude/scripts/test-scaffold.sh	14	# Usage: bash .claude/scripts/test-scaffold.sh ENGINE [--dry-run \| --list] [--root DIR]	COMMENT
MEDIUM	.claude/scripts/test-scaffold.sh	19	# --list print the project-relative paths this engine's scaffold	COMMENT
MEDIUM	.claude/scripts/gdd-structure-check.sh	5	# hallucinate a missing section. This is the cheapest real win available: the	COMMENT
MEDIUM	docs/registry/architecture.yaml	178	# Use dependency injection or signals instead."	COMMENT

AI Slop Vocabulary3 hits · 9 pts

Severity	File	Line	Snippet	Context
MEDIUM	.claude/hooks/yaml-helper.sh	457	# That is not a test-harness artifact. Any real project nested inside another	COMMENT
MEDIUM	.claude/hooks/session-start.sh	37	# Observed on real harness events as a single line of JSON with session_id,	COMMENT
MEDIUM	.claude/hooks/session-start.sh	39	# Do NOT read stdin here unboundedly -- the harness may leave it open, and a	COMMENT

Redundant / Tautological Comments5 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	.claude/statusline.sh	110	# Check if engine is configured (project.yaml first, fall back to technical-preferences.md)	COMMENT
LOW	.claude/hooks/validate-push.sh	241	# Check if pushing to a protected branch: main, master, or any release/*	COMMENT
LOW	.claude/hooks/detect-gaps.sh	46	# Check if engine is configured (project.yaml first, fall back to technical-preferences.md)	COMMENT
LOW	.claude/hooks/detect-gaps.sh	61	# Check if a design record exists.	COMMENT
LOW	.claude/hooks/detect-gaps.sh	77	# Check if source code exists.	COMMENT

Example Usage Blocks4 hits · 6 pts

Severity	File	Line	Snippet	Context
LOW	.claude/hooks/yaml-helper.sh	70	# Usage:	COMMENT
LOW	.claude/scripts/rotate-session-state.sh	21	# Usage:	COMMENT
LOW	.claude/scripts/gdd-structure-check.sh	24	# Usage:	COMMENT
LOW	.claude/scripts/review-receipts.sh	41	# Usage:	COMMENT

Fake / Example Data1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	studio-tests/agents/specialists/writer.md	36	- Does not produce even partial world history as a "placeholder"	CODE

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	.claude/hooks/validate-commit.sh	558	except Exception:	CODE

Donchitos/Claude-Code-Game-Studios

Open-Source Code Quality, Security and Technical Debt Review