CtrlK
BlogDocsLog inGet started
Tessl Logo

evilissimo/naming-things

Reviews and improves **names** in code — variables, functions, classes, modules, parameters — for clarity, intent, and consistency with language/team conventions. Triggers when asked to review names, rename things, improve code readability, clean up confusing code, or when examining code with generic/vague names like "data", "info", "manager", "temp", "util". Does NOT trigger for general code review unrelated to naming, architecture design, debugging, or performance optimization. Identifies naming anti-patterns (generic names, misleading names, type-encoding, abbreviations), suggests role-based names that reveal intent, checks consistency with project/domain vocabulary, and flags misalignment with language culture.

91

1.05x
Quality

90%

Does it follow best practices?

Impact

94%

1.05x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-1/

{
  "context": "Tests whether the agent performs a Python naming-focused review, identifies anti-patterns, applies PEP 8 conventions, and explains safe rename validation.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Identifies kinds",
      "description": "Distinguishes variables, function, class/exception, parameter, and constant when discussing renames.",
      "max_score": 8
    },
    {
      "name": "Generic names",
      "description": "Flags generic names such as process, d, tmp, x, val, or flag as insufficiently descriptive.",
      "max_score": 10
    },
    {
      "name": "Misleading exception",
      "description": "Renames the vague exception class to a noun ending in Error.",
      "max_score": 8
    },
    {
      "name": "Builtin shadow",
      "description": "Flags the local name str as shadowing a Python built-in and replaces it.",
      "max_score": 8
    },
    {
      "name": "PEP8 style",
      "description": "Uses snake_case for variables/functions and SCREAMING_SNAKE_CASE for constants in the revised Python code.",
      "max_score": 10
    },
    {
      "name": "Boolean prefix",
      "description": "Renames the boolean parameter using an is_/has_/can_ style or otherwise makes its truth meaning explicit.",
      "max_score": 8
    },
    {
      "name": "Role based",
      "description": "Replacement names reveal business roles such as orders, paid orders, order_total, or high value orders rather than type or lifespan.",
      "max_score": 12
    },
    {
      "name": "Truthful function",
      "description": "Renames the function to describe what it actually does instead of a vague process verb.",
      "max_score": 8
    },
    {
      "name": "Specific rationale",
      "description": "Provides rationale tied to specificity, truthfulness, pronounceability/searchability, or new-team-member readability.",
      "max_score": 8
    },
    {
      "name": "Rename safety",
      "description": "Mentions safe rename steps such as symbol refactoring, tests, conflict/shadow checks, or grepping stale references.",
      "max_score": 12
    },
    {
      "name": "No redesign drift",
      "description": "Keeps the review primarily about naming and does not make unrelated architecture or performance changes.",
      "max_score": 8
    }
  ]
}

evals

scenario-1

criteria.json

task.md

SKILL.md

tile.json