Skip to content
Back to skills

Code Standards Detective

ASecurity

Deep codebase analysis to discover actual coding standards through statistical evidence. Use when analyzing naming conventions, import patterns, or detecting anti-patterns in existing code. Provides evidence-based detection of how the codebase actually works (not aspirations).

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
toolstypescriptgobash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill code-standards-detective --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Standards Detective?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Standards Detective
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-code-standards-detective/badge)](https://www.skillsdirectory.com/skills/david-li0406-code-standards-detective)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-standards-detective
description: Deep codebase analysis to discover actual coding standards through statistical evidence. Use when analyzing naming conventions, import patterns, or detecting anti-patterns in existing code. Provides evidence-based detection of how the codebase actually works (not aspirations).
allowed-tools: Read, Grep, Glob, Bash, Write
---

# Code Standards Detective Skill

## Overview

You analyze codebases to discover and document coding standards. You detect patterns, conventions, and anti-patterns with statistical evidence.

## Progressive Disclosure

Load phases as needed:

| Phase | When to Load | File |
|-------|--------------|------|
| Config Analysis | Parsing config files | `phases/01-config-analysis.md` |
| Pattern Detection | Finding code patterns | `phases/02-pattern-detection.md` |
| Report Generation | Creating standards doc | `phases/03-report.md` |

## Core Principles

1. **Evidence-based** - Statistics and confidence levels
2. **Real examples** - Code snippets from actual codebase
3. **Actionable** - Clear guidelines, not just observations

## Quick Reference

### Detection Categories

1. **Naming Conventions**
   - Variables: camelCase, PascalCase, UPPER_SNAKE
   - Functions: verb prefixes (get, set, is, has)
   - Files: kebab-case, PascalCase

2. **Import Patterns**
   - Absolute vs relative imports
   - Import ordering
   - Named vs default exports

3. **Function Characteristics**
   - Average length
   - Parameter counts
   - Return type patterns

4. **Type Usage**
   - any usage percentage
   - Interface vs type
   - Strictness level

5. **Error Handling**
   - try-catch patterns
   - Error types used
   - Logging patterns

### Config Files to Parse

```
.eslintrc.js / .eslintrc.json
.prettierrc / .prettierrc.json
tsconfig.json
.editorconfig
```

### Output Format

```markdown
# Coding Standards: [Project Name]

## Naming Conventions

### Variables
**Pattern**: camelCase
**Confidence**: 94% (842/896 samples)
**Example**:
```typescript
const userName = 'John';
const isActive = true;
```

### Functions
**Pattern**: verb + noun (getUser, setConfig)
**Confidence**: 87% (234/269 samples)

## Import Patterns
**Absolute imports**: Enabled (paths in tsconfig)
**Import order**: external → internal → relative
**Example**:
```typescript
import { z } from 'zod';           // external
import { logger } from '@/lib';    // internal
import { helper } from './helper'; // relative
```

## Anti-Patterns Detected
- ⚠️ `any` usage: 12 instances (recommend: 0)
- ⚠️ console.log: 8 instances (use logger)
```

## Workflow

1. **Parse configs** (< 500 tokens): ESLint, Prettier, TypeScript
2. **Detect patterns** (< 600 tokens per category): With stats
3. **Generate report** (< 600 tokens): Standards document

## Token Budget

**NEVER exceed 2000 tokens per response!**

## Detection Commands

```bash
# Count naming patterns
grep -rE "const [a-z][a-zA-Z]+ =" src/ | wc -l

# Find function patterns
grep -rE "function (get|set|is|has)" src/ | head -20

# Check for any usage
grep -rE ": any" src/ | wc -l
```

Files in this skill

  • MEMORY.md182 B
  • SKILL.md3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…