tessl-labs/skill-discovery
Discover and apply best practice skills automatically. Gap analysis scans the codebase, skill-search fills gaps from the registry, skill-classifier separates proactive from reactive skills, quality-standards generates CLAUDE.md guidance, self-review compares code against checklists, and verification-strategy sets up test/lint/typecheck feedback loops.
86
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
SKILL.mdskills/self-review/
- name:
- self-review
- description:
- Compare your code against installed proactive skill checklists and fix gaps. Use after committing, after completing a feature, before submitting a PR, or whenever you want to verify your code meets quality standards. Can be triggered by a post-commit hook, a periodic check, or a direct request like "review your code", "check quality", "did you follow the skills".
- metadata:
- {"author":"tessl-labs","version":"0.1.0","tags":["tessl","discovery","review","quality","self-check"]}
Self-Review
Read your installed proactive skill checklists, then read your own code, and fix any gaps. This comparative approach — reading the standard, then reading the code — produces the highest code quality.
Why This Works
Agents that read skill checklists and then examine their own code catch significantly more gaps than agents that rely on memory alone. The act of re-reading the concrete checklist items alongside the actual source files surfaces missing patterns that would otherwise be overlooked.
When to Run
- After a git commit (a post-commit hook can suggest this)
- After completing a feature or task
- Before submitting a pull request
- When prompted by a hook, a user, or your own judgment
- Periodically during long coding sessions
This skill is not tied to git. It works any time you want to verify your code against quality standards.
Workflow
Step 1 — Get Proactive Skills List
Read .skill-discovery-state.json and get the proactiveSkills array. These are the skills whose patterns should be present in all code.
cat .skill-discovery-state.jsonIf proactiveSkills is empty or missing, fall back to reading ALL installed SKILL.md files:
find .tessl/tiles -name "SKILL.md" 2>/dev/nullStep 2 — Read Every Proactive Skill's Checklist
For each proactive skill, open its SKILL.md and find the ## Checklist section. Read every item. These are the patterns that must be present in your code.
Do not skim. Read each checklist item carefully.
Step 3 — Read Your Own Code
For each checklist item, identify which source file(s) it applies to and read them. Look for the specific pattern described in the checklist item.
| Checklist item | Where to look |
|---|---|
| Error-handling middleware registered | Server setup file (app.ts, server.ts, main.py) |
| Security headers (helmet) configured | Server setup file |
| Structured logger, not console.log | All source files — grep for console.log |
| ARIA attributes on interactive elements | All component/template files |
| Error boundaries in place | React component tree, layout files |
| Tests exist and pass | Test directory, run test command |
| Indexes on foreign key columns | Database schema/migration files |
| Health check endpoint | Routes file |
Step 4 — Fix Missing Patterns
For every checklist item that is not present in your code, fix it now. An installed proactive skill whose patterns are absent from the code is a quality gap.
List what you checked and what you fixed so you have a record.
Step 5 — Verify
After fixing, run verification (tests, type check, lint, build) to confirm your fixes don't break anything.
What NOT to Review
- Reactive skills — Only review proactive skills. Reactive skills (SQLite patterns, JWT implementation) apply only when you're actively working in that domain, not on every review.
- Skills you didn't install — Only review skills that are actually installed in
.tessl/tiles/.
Checklist
For each proactive skill:
- Read its full Checklist section
- For each item, read the relevant source file
- Confirm the pattern is present, or fix it
- Run verification after fixes