Skip to content
Steve Morin

/factor-scan

Sweep a code area for bugs, smells, and architectural drift.

What it does

A broad sweep over an area of code that surfaces three different classes of problem at once — outright bugs, quality issues, and architectural smells — then walks you through the findings one at a time rather than dumping a report. What survives the walk becomes an inline spec ready to hand straight to a planning skill.

When to reach for it

Inheriting unfamiliar code, or when a module has been edited by enough people that nobody is confident in it any more.

It's working if

  • You reject some findings, and rejecting them is fast.
  • The output is a spec you can act on, not a list you file.
  • It finds at least one thing you would have shipped.

Install this skill

Then type /factor-scan in your agent.

npx skills@latest add smorinlabs/smorinlabs-harness -s factor-scan

Or install the whole factor-harness plugin — this skill plus 3 others.

/plugin install factor-harness@smorinlabs-harness

Where it fits

  • /factor-architect — the deeper pass when the problem turns out to be structural.
  • /factor-dedup — where the scan sends you when the smell is "we have four of these".
  • /using-factor-harness — routes you here when you are not sure which of the three you want.