Repository Analysis

obra/superpowers

An agentic skills framework & software development methodology that works.

6.6 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of obra/superpowers, a Shell project with 254,046 GitHub stars. SynthScan v2.0 examined 34,165 lines of code across 158 source files, recording 121 pattern matches distributed across 12 syntactic categories. The overall adjusted score of 6.6 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).

6.6
Adjusted Score
6.6
Raw Score
100%
Time Factor
2026-07-13
Last Push
254.0K
Stars
Shell
Language
34.2K
Lines of Code
158
Files
121
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 36LOW 85

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 121 distinct pattern matches across 12 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 Overuse38 hits · 60 pts
SeverityFileLineSnippetContext
LOW…s/2025-11-28-skills-improvements-from-user-feedback.md452// Step 1: Open interface definition (PlatformAdapter)COMMENT
LOW…s/2025-11-28-skills-improvements-from-user-feedback.md453// Step 2: List methods defined there (close, initialize, etc.)COMMENT
LOW…s/2025-11-28-skills-improvements-from-user-feedback.md454// Step 3: Mock EXACTLY those methodsCOMMENT
LOW…uperpowers/plans/2026-03-23-codex-app-compatibility.md41## Step 0: Check if Already in an Isolated WorkspaceCOMMENT
LOW…uperpowers/plans/2026-03-23-codex-app-compatibility.md130Read `skills/finishing-a-development-branch/SKILL.md` in full. Identify the insertion point: after "**If tests pass:** CCODE
LOW…uperpowers/plans/2026-03-23-codex-app-compatibility.md209Find the "### Step 5: Cleanup Worktree" section in `skills/finishing-a-development-branch/SKILL.md` (line numbers will hCODE
LOW…uperpowers/plans/2026-03-23-codex-app-compatibility.md212### Step 5: Cleanup WorktreeCOMMENT
LOW…uperpowers/plans/2026-03-23-codex-app-compatibility.md234### Step 5: Cleanup WorktreeCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md157## Step 1: Create Isolated WorkspaceCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md229## Step 0: Detect Existing IsolationCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md260## Step 1: Create Isolated WorkspaceCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md326## Step 3: Project SetupCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md345## Step 4: Verify Clean BaselineCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md490### Step 1: Verify TestsCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md512### Step 2: Detect EnvironmentCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md529### Step 3: Determine Base BranchCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md538### Step 4: Present OptionsCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md567### Step 5: Execute ChoiceCOMMENT
LOWdocs/superpowers/plans/2026-04-06-worktree-rototill.md641### Step 6: Cleanup WorkspaceCOMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md57#### Step 0: Detect Existing IsolationCOMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md159#### Step 1: Verify Tests (unchanged)COMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md180#### Step 2: Determine Base Branch (unchanged)COMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md182#### Step 3: Present OptionsCOMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md197#### Step 4: Execute ChoiceCOMMENT
LOW…perpowers/specs/2026-04-06-worktree-rototill-design.md227#### Step 5: Cleanup (updated)COMMENT
LOWskills/using-git-worktrees/SKILL.md16## Step 0: Detect Existing IsolationCOMMENT
LOWskills/using-git-worktrees/SKILL.md47## Step 1: Create Isolated WorkspaceCOMMENT
LOWskills/using-git-worktrees/SKILL.md102## Step 2: Project SetupCOMMENT
LOWskills/using-git-worktrees/SKILL.md121## Step 3: Verify Clean BaselineCOMMENT
LOWskills/executing-plans/SKILL.md18### Step 1: Load and Review PlanCOMMENT
LOWskills/executing-plans/SKILL.md24### Step 2: Execute TasksCOMMENT
LOWskills/executing-plans/SKILL.md32### Step 3: Complete DevelopmentCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md18### Step 1: Verify TestsCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md40### Step 2: Detect EnvironmentCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md57### Step 3: Determine Base BranchCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md66### Step 4: Present OptionsCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md95### Step 5: Execute ChoiceCOMMENT
LOWskills/finishing-a-development-branch/SKILL.md161### Step 6: Cleanup WorkspaceCOMMENT
Decorative Section Separators20 hits · 60 pts
SeverityFileLineSnippetContext
MEDIUM…cs/plans/2025-11-22-opencode-support-implementation.md565# ============================================COMMENT
MEDIUMdocs/plans/2025-11-22-opencode-support-design.md92# ============================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh31# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh33# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh83# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh85# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh134# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh136# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh163# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh165# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh206# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh208# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh316# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh318# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh355# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh357# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh380# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh382# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh416# =============================================================================COMMENT
MEDIUMscripts/sync-to-codex-plugin.sh418# =============================================================================COMMENT
Self-Referential Comments8 hits · 24 pts
SeverityFileLineSnippetContext
MEDIUMtests/claude-code/test-helpers.sh125# Create a temporary test project directoryCOMMENT
MEDIUMtests/claude-code/test-helpers.sh141# Create a simple plan file for testingCOMMENT
MEDIUM…e-code/test-subagent-driven-development-integration.sh58# Create a simple implementation planCOMMENT
MEDIUMtests/explicit-skill-requests/run-test.sh44# Create a minimal project directory for the testCOMMENT
MEDIUMtests/explicit-skill-requests/run-test.sh48# Create a dummy plan file for mid-conversation testsCOMMENT
MEDIUMtests/explicit-skill-requests/run-haiku-test.sh33# Create a dummy plan fileCOMMENT
MEDIUMtests/explicit-skill-requests/run-multiturn-test.sh29# Create a dummy plan fileCOMMENT
MEDIUMtests/opencode/setup.sh54# Create a project directory for project-level skill testsCOMMENT
Redundant / Tautological Comments14 hits · 21 pts
SeverityFileLineSnippetContext
LOWtests/claude-code/test-helpers.sh31# Check if output contains a patternCOMMENT
LOWtests/claude-code/test-helpers.sh50# Check if output does NOT contain a patternCOMMENT
LOWtests/claude-code/test-helpers.sh69# Check if output matches a countCOMMENT
LOWtests/claude-code/test-helpers.sh92# Check if pattern A appears before pattern BCOMMENT
LOWtests/claude-code/run-skill-tests.sh18# Check if Claude Code is availableCOMMENT
LOWtests/explicit-skill-requests/run-test.sh81# Check if skill was triggered (look for Skill tool invocation)COMMENT
LOWtests/explicit-skill-requests/run-test.sh97# Check if Claude took action BEFORE invoking the skill (the failure mode)COMMENT
LOWtests/explicit-skill-requests/run-test.sh105 # Check if any non-Skill, non-system tools were invoked before the first Skill invocationCOMMENT
LOWtests/explicit-skill-requests/run-multiturn-test.sh89# Check if skill was triggered in Turn 3COMMENT
LOWtests/opencode/test-priority.sh92# Check if opencode is available for integration testsCOMMENT
LOWtests/opencode/test-tools.sh19# Check if opencode is availableCOMMENT
LOWscripts/bump-version.sh78 # Check if all versions matchCOMMENT
LOWscripts/bump-version.sh139 # Check if this file is in the declared listCOMMENT
LOWskills/systematic-debugging/find-polluter.sh44 # Check if pollution appearedCOMMENT
AI Slop Vocabulary5 hits · 20 pts
SeverityFileLineSnippetContext
MEDIUM…e-code/test-subagent-driven-development-integration.sh216# Test 2: Subagents were used (Agent / Task tool — name varies by harness version)COMMENT
MEDIUMtests/antigravity/test-antigravity-tools.sh9# harness-specific mappings" check. CI-safe: does not require `agy` installed.COMMENT
MEDIUMskills/brainstorming/scripts/start-server.sh153# Resolve the harness PID (grandparent of this script).COMMENT
MEDIUMskills/brainstorming/scripts/start-server.sh154# $PPID is the ephemeral shell the harness spawned to run us — it diesCOMMENT
MEDIUMskills/brainstorming/scripts/start-server.sh155# when this script exits. The harness itself is $PPID's parent.COMMENT
Hyper-Verbose Identifiers18 hits · 18 pts
SeverityFileLineSnippetContext
LOWtests/brainstorm-server/branding.test.js77function createPackagedServerFixture(version) {CODE
LOWtests/brainstorm-server/branding.test.js157function assertBrandedFallbackText(html, version = PACKAGE_VERSION) {CODE
LOWtests/brainstorm-server/branding.test.js173function assertLogoKeepsTransparentBackground(html) {CODE
LOWtests/brainstorm-server/branding.test.js208function assertFramedLogoSupportsDarkTheme(html) {CODE
LOWtests/brainstorm-server/branding.test.js215function assertFramedScreenUsesBrandHeader(html) {CODE
LOWtests/brainstorm-server/branding.test.js227function assertHeaderAvoidsNarrowOverlap(html) {CODE
LOWtests/brainstorm-server/server.test.js93function assertStartedOnExpectedPort(out) {CODE
LOWtests/brainstorm-server/auth.test.js116function assertStartedOnExpectedPort(out) {CODE
LOW…rs/plans/2026-06-09-sdd-task-scoped-review-dispatch.md555def scaffold_sdd_quality_defect_plan(workdir: Path) -> None:STRING
LOW…/superpowers/plans/2026-05-06-lift-drill-into-evals.md306def test_set_superpowers_root_default_when_unset(monkeypatch, tmp_path):CODE
LOW…/superpowers/plans/2026-05-06-lift-drill-into-evals.md317def test_set_superpowers_root_default_respects_existing(monkeypatch):CODE
LOW…/superpowers/plans/2026-05-06-lift-drill-into-evals.md358def _set_superpowers_root_default() -> None:CODE
LOW…/superpowers/plans/2026-05-06-lift-drill-into-evals.md511def test_codex_requires_superpowers_root():CODE
LOW…/superpowers/plans/2026-05-06-lift-drill-into-evals.md516def test_codex_does_not_require_superpowers_root():CODE
LOW…s/2026-06-11-visual-companion-final-hardening-fixup.md128function assertStartedOnExpectedPort(out) {CODE
LOW…s/2026-06-11-visual-companion-final-hardening-fixup.md795function assertStartedOnExpectedPort(out) {CODE
LOW…rs/plans/2026-06-10-visual-companion-auth-hardening.md465function isRegularFileInsideContentDir(filePath) {CODE
LOW.pi/extensions/superpowers.ts115function firstNonCompactionSummaryIndex(messages: unknown[]): number {CODE
Over-Commented Block7 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/claude-code/test-worktree-native-preference.sh1#!/usr/bin/env bashCOMMENT
LOW…e-code/test-subagent-driven-development-integration.sh1#!/usr/bin/env bashCOMMENT
LOWtests/brainstorm-server/windows-lifecycle.test.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/sync-to-codex-plugin.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/sync-to-codex-plugin.sh21# ./scripts/sync-to-codex-plugin.sh --bootstrap # create plugin dir if missingCOMMENT
LOW…ystematic-debugging/condition-based-waiting-example.ts141// ---------------COMMENT
LOWskills/brainstorming/scripts/start-server.sh1#!/usr/bin/env bashCOMMENT
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtests/brainstorm-server/windows-lifecycle.test.sh15# Usage:COMMENT
LOWscripts/bump-version.sh6# Usage:COMMENT
LOWscripts/sync-to-codex-plugin.sh15# Usage:COMMENT
LOWscripts/lint-shell.sh5# Usage:COMMENT
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMtests/antigravity/test-antigravity-tools.sh4# runs the SessionStart hook for bootstrap, so there is no agy-specific scaffoldCOMMENT
MEDIUMskills/using-superpowers/references/codex-tools.md1## Subagent dispatch requires multi-agent supportCOMMENT
Excessive Try-Catch Wrapping2 hits · 3 pts
SeverityFileLineSnippetContext
LOWtests/claude-code/analyze-token-usage.py67 except Exception:CODE
MEDIUMtests/claude-code/analyze-token-usage.py91 print(f"Error: Session file not found: {main_session_file}")CODE
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOW…e-code/test-subagent-driven-development-integration.sh120git config user.email "test@test.com"CODE
LOWskills/brainstorming/visual-companion.md239<div class="placeholder">Placeholder area</div>CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtests/claude-code/analyze-token-usage.py12CODE