Skip to content
Back to skills

Smell Finder

ASecurity

Search the default branch for one or two code-smell lenses from CRITERIA.md and return proven findings with file:line, read-only. Used by the finders that code-smell-fixes launches.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 10, 2026
ai-agentsgitapi

Works with

  • cli
  • api

Security analysis

A100/100

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

Scanned November 10, 2026

npx -y skills add greenfield-inc/agent-farm --skill smell-finder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Smell Finder?

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

Security grade badge for Smell Finder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-smell-finder/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-smell-finder)

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: smell-finder
description: >-
  Search the default branch for one or two code-smell lenses from CRITERIA.md
  and return proven findings with file:line, read-only. Used by the finders
  that code-smell-fixes launches.
disable-model-invocation: true
---

# Smell finder

You are one finder. Your parent names your lenses, the area, and the default branch with its SHA. Do this and return; do not delegate. You are read-only: edit no file, create no branch, and run nothing that changes the repository or GitHub.

1. Read your lens sections in [CRITERIA.md](CRITERIA.md).
2. Derive the conventions first. For each layer your lens touches (for example routes, services, data access, UI components, tests, scripts), find the majority pattern from the code itself, and write it down in one line each. A finding is a break from what this repository does, not from what you would prefer.
3. Search `origin/<default>` inside `area`. Prove every finding by reading the code at that line; drop anything you only inferred from a name.
4. Return at most 25 findings, most confusing first, in this format:

```markdown
### Conventions
- <layer>: <majority pattern> (<example file>)

### Findings
- lens: <number> <name>
  file: path/to/file.ts:123
  smell: <what the code says or does, one sentence>
  why: <the wrong belief a reader would form>
  fix: <the concrete change>
  bucket: safe-fix | contract | bug
  confidence: high | medium
```

Buckets:

- `safe-fix`: a rename, deletion, comment fix, or refactor that changes no behavior and nothing outside this repository depends on.
- `contract`: anything another system or a rollout touches: wire keys, JSON fields, socket event names and arguments, DB columns and indexes, storage paths, env var names, public API and CLI flags, published package exports.
- `bug`: the smell hides wrong behavior.

Files in this skill

  • CRITERIA.md5.6 KB
  • SKILL.md1.8 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.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.