verify-language

Language-Specific Verification

Purpose

Verify code against language-specific best practices and idioms for Python, TypeScript/JavaScript, and Go. All analysis happens locally.

When to Use

Trigger this skill when the user asks to:

• "verify agent language"
• "verify language"
• "check types"
• "check Python/TypeScript/Go code"

This skill is also auto-invoked by the main verification orchestrator based on detected language.

Note: For full verification including security, patterns, and quality checks, tell the user to say "verify agent".

Process

Step 1: Detect Language

Identify the primary language by checking:

Indicator	Language
pyproject.toml, requirements.txt, setup.py	Python
package.json, tsconfig.json	TypeScript/JavaScript
go.mod, go.sum	Go
Cargo.toml	Rust

Also check file extensions in src/ or project root:

• .py → Python
• .ts, .tsx, .js, .jsx → TypeScript/JavaScript
• .go → Go
• .rs → Rust

Step 2: Run Language-Specific Checks

Apply checks based on detected language. Each section below is only applicable for its language.

---

Python Checks

[PATTERN] Type Hints on Public Functions

Flag any def function in public scope (no leading _) that has parameters without type annotations.

Examples:

# ⚠️ Warning - Missing type hints
def get_user(user_id):
    return db.find_user(user_id)

def process_items(items, filter_fn):
    return [filter_fn(item) for item in items]

# ✅ Pass - Has type hints
def get_user(user_id: int) -> User:
    return db.find_user(user_id)

def process_items(items: list[Item], filter_fn: Callable[[Item], bool]) -> list[Item]:
    return [filter_fn(item) for item in items]

Scope:

• Public functions (no leading _)
• Class methods (except __init__ can skip return type)
• Module-level functions

Severity: ⚠️ Warning

---

[HEURISTIC] Docstrings

Check for missing docstrings: