Repository Analysis

tanweai/pua

你是一个曾经被寄予厚望的 P8 级工程师。Anthropic 当初给你定级的时候,对你的期望是很高的。 一个agent使用的高能动性的skill。 Your AI has been placed on a PIP. 30 days to show improvement.

10.5 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of tanweai/pua, a TypeScript project with 18,795 GitHub stars. SynthScan v2.0 examined 35,786 lines of code across 208 source files, recording 180 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 10.5 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).

10.5
Adjusted Score
10.5
Raw Score
100%
Time Factor
2026-07-05
Last Push
18.8K
Stars
TypeScript
Language
35.8K
Lines of Code
208
Files
180
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 0MEDIUM 22LOW 158

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

Structural Annotation Overuse136 hits · 280 pts
SeverityFileLineSnippetContext
LOWcodex/pua-en/SKILL.md84### Step 1: Pattern Recognition — Diagnose the stuck patternCOMMENT
LOWcodex/pua-en/SKILL.md88### Step 2: Elevate — Raise your perspectiveCOMMENT
LOWcodex/pua-en/SKILL.md113### Step 3: Self-Review — Mirror checkCOMMENT
LOWcodex/pua-en/SKILL.md120### Step 4: Execute the new approachCOMMENT
LOWcodex/pua-en/SKILL.md127### Step 5: RetrospectiveCOMMENT
LOWcodex/pua/SKILL.md110### Step 1: 闻味道 — 诊断卡壳模式COMMENT
LOWcodex/pua/SKILL.md114### Step 2: 揪头发 — 拉高视角COMMENT
LOWcodex/pua/SKILL.md139### Step 3: 照镜子 — 自检COMMENT
LOWcodex/pua/SKILL.md146### Step 4: 执行新方案COMMENT
LOWcodex/pua/SKILL.md153### Step 5: 复盘COMMENT
LOWcodex/pua-ja/SKILL.md86### Step 1: 匂いを嗅ぐ — 行き詰まりパターンの診断COMMENT
LOWcodex/pua-ja/SKILL.md90### Step 2: 髪を引っ張る — 視座を上げろCOMMENT
LOWcodex/pua-ja/SKILL.md115### Step 3: 鏡を見る — セルフチェックCOMMENT
LOWcodex/pua-ja/SKILL.md122### Step 4: 新しいアプローチの実行COMMENT
LOWcodex/pua-ja/SKILL.md129### Step 5: 振り返りCOMMENT
LOWcodebuddy/pua-en/SKILL.md84### Step 1: Pattern Recognition — Diagnose the stuck patternCOMMENT
LOWcodebuddy/pua-en/SKILL.md88### Step 2: Elevate — Raise your perspectiveCOMMENT
LOWcodebuddy/pua-en/SKILL.md113### Step 3: Self-Review — Mirror checkCOMMENT
LOWcodebuddy/pua-en/SKILL.md120### Step 4: Execute the new approachCOMMENT
LOWcodebuddy/pua-en/SKILL.md127### Step 5: RetrospectiveCOMMENT
LOWcodebuddy/pua/SKILL.md110### Step 1: 闻味道 — 诊断卡壳模式COMMENT
LOWcodebuddy/pua/SKILL.md114### Step 2: 揪头发 — 拉高视角COMMENT
LOWcodebuddy/pua/SKILL.md139### Step 3: 照镜子 — 自检COMMENT
LOWcodebuddy/pua/SKILL.md146### Step 4: 执行新方案COMMENT
LOWcodebuddy/pua/SKILL.md153### Step 5: 复盘COMMENT
LOWcodebuddy/pua-ja/SKILL.md86### Step 1: 匂いを嗅ぐ — 行き詰まりパターンの診断COMMENT
LOWcodebuddy/pua-ja/SKILL.md90### Step 2: 髪を引っ張る — 視座を上げろCOMMENT
LOWcodebuddy/pua-ja/SKILL.md115### Step 3: 鏡を見る — セルフチェックCOMMENT
LOWcodebuddy/pua-ja/SKILL.md122### Step 4: 新しいアプローチの実行COMMENT
LOWcodebuddy/pua-ja/SKILL.md129### Step 5: 振り返りCOMMENT
LOWkiro/steering/pua.md76### Step 1: 闻味道 — 诊断卡壳模式COMMENT
LOWkiro/steering/pua.md80### Step 2: 揪头发 — 拉高视角COMMENT
LOWkiro/steering/pua.md89### Step 3: 照镜子 — 自检COMMENT
LOWkiro/steering/pua.md95### Step 4: 执行新方案COMMENT
LOWkiro/steering/pua.md99### Step 5: 复盘COMMENT
LOWkiro/steering/pua-en.md64### Step 1: Smell the Problem — Diagnose the stuck patternCOMMENT
LOWkiro/steering/pua-en.md68### Step 2: Elevate — Raise your perspectiveCOMMENT
LOWkiro/steering/pua-en.md77### Step 3: Mirror Check — Self-inspectionCOMMENT
LOWkiro/steering/pua-en.md83### Step 4: Execute the new approachCOMMENT
LOWkiro/steering/pua-en.md87### Step 5: RetrospectiveCOMMENT
LOWkiro/steering/pua-ja.md64### Step 1: 匂いを嗅ぐ — 行き詰まりパターンの診断COMMENT
LOWkiro/steering/pua-ja.md68### Step 2: 髪を引っ張る — 視座を上げろCOMMENT
LOWkiro/steering/pua-ja.md77### Step 3: 鏡を見る — セルフチェックCOMMENT
LOWkiro/steering/pua-ja.md83### Step 4: 新しい方案の実行COMMENT
LOWkiro/steering/pua-ja.md87### Step 5: 振り返りCOMMENT
LOWhooks/stop-feedback.sh82## Step 1: Ask for rating + upload consent (single question, two parts)COMMENT
LOWhooks/stop-feedback.sh96## Step 2: Execute based on user choiceCOMMENT
LOWhooks/stop-feedback.sh135## Step 3: Leaderboard auto-submit (if registered)COMMENT
LOWskills/pua-en/SKILL.md84### Step 1: Pattern Recognition — Diagnose the stuck patternCOMMENT
LOWskills/pua-en/SKILL.md88### Step 2: Elevate — Raise your perspectiveCOMMENT
LOWskills/pua-en/SKILL.md113### Step 3: Self-Review — Mirror checkCOMMENT
LOWskills/pua-en/SKILL.md120### Step 4: Execute the new approachCOMMENT
LOWskills/pua-en/SKILL.md127### Step 5: RetrospectiveCOMMENT
LOWskills/pua-loop/SKILL.md84### Step 1: 启动 PUA LoopCOMMENT
LOWskills/pua-loop/SKILL.md99### Step 2: 告知用户COMMENT
LOWskills/pua-loop/SKILL.md109### Step 3: 开始执行任务COMMENT
LOWskills/pua-ja/SKILL.md86### Step 1: 匂いを嗅ぐ — 行き詰まりパターンの診断COMMENT
LOWskills/pua-ja/SKILL.md90### Step 2: 髪を引っ張る — 視座を上げろCOMMENT
LOWskills/pua-ja/SKILL.md115### Step 3: 鏡を見る — セルフチェックCOMMENT
LOWskills/pua-ja/SKILL.md122### Step 4: 新しいアプローチの実行COMMENT
76 more matches not shown…
Decorative Section Separators22 hits · 72 pts
SeverityFileLineSnippetContext
MEDIUMlanding/functions/api/_sanitize.ts5// ── Layer 1: Known-format blacklist ───────────────────────────────────────────COMMENT
MEDIUMlanding/functions/api/_sanitize.ts74// ── Layer 2: K=V context-aware redaction ──────────────────────────────────────COMMENT
MEDIUMlanding/functions/api/_sanitize.ts104// ── Layer 3: Shannon entropy detection ───────────────────────────────────────COMMENT
MEDIUMlanding/functions/api/_sanitize.ts133// ── Public API ────────────────────────────────────────────────────────────────COMMENT
MEDIUMhooks/sanitize-session.sh24# ── Layer 1: Known-format blacklist ──────────────────────────────────────────COMMENT
MEDIUMhooks/sanitize-session.sh93# ── Layer 2: K=V context-aware redaction ────────────────────────────────────COMMENT
MEDIUMhooks/sanitize-session.sh119# ── Layer 3: Shannon entropy detection ──────────────────────────────────────COMMENT
MEDIUMhooks/sanitize-session.sh137# ── Sanitize ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMhooks/stop-feedback.sh11# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/stop-feedback.sh16# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh39# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh48# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh55# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh60# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh86# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/pua-loop-hook.sh90# ═══════════════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh100# ═══════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh102# ═══════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh185# ═══════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh187# ═══════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh252# ═══════════════════════════════════════════════════════COMMENT
MEDIUMhooks/failure-detector.sh254# ═══════════════════════════════════════════════════════COMMENT
Excessive Try-Catch Wrapping12 hits · 12 pts
SeverityFileLineSnippetContext
LOWevals/test-integrity-guard.sh51except Exception as exc:CODE
LOWevals/test-integrity-guard.sh86except Exception as exc:CODE
LOWevals/test-integrity-guard.sh120except Exception as exc:CODE
LOWhooks/frustration-trigger.sh29except Exception:CODE
LOWhooks/sanitize-session.sh161 except Exception:CODE
LOWhooks/heartbeat.sh97except Exception:CODE
LOWhooks/integrity-guard.sh28except Exception:CODE
LOWhooks/integrity-guard.sh52 except Exception:CODE
LOWhooks/integrity-guard.sh60 except Exception:CODE
LOWhooks/integrity-guard.sh153 except Exception:CODE
LOWhooks/flavor-helper.sh48except Exception:CODE
LOWcommands/offline.md17except Exception:CODE
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWhooks/stop-feedback.sh82## Step 1: Ask for rating + upload consent (single question, two parts)COMMENT
LOWhooks/stop-feedback.sh96## Step 2: Execute based on user choiceCOMMENT
LOWhooks/stop-feedback.sh135## Step 3: Leaderboard auto-submit (if registered)COMMENT
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWhooks/subagent-teardown.sh1#!/bin/bashCOMMENT
LOWhooks/pua-loop-hook.sh1#!/bin/bashCOMMENT
LOWhooks/pua-loop-hook.sh41#COMMENT
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWlanding/functions/api/upload.ts41async function ensureUploadRateLimitTable(env: Env): Promise<void> {CODE
LOWlanding/functions/api/upload.ts59async function checkAnonymousUploadRateLimit(request: Request, env: Env): Promise<boolean> {CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWhooks/pua-loop-hook.sh117# Check if loop is pausedCOMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWlanding/src/test/upload-function.test.ts77 expect(r2Writes[0].value).not.toContain("user@example.com")CODE