Public surface sweeper

Release hygiene made visible.

This sample shows the product shape: scan a repository's public-facing surface, flag anything that would spoil a good first impression, and turn it into concrete action items before a client, employer, or evaluator sees the project.

View repository Pilot overview

Blocker

Missing public contract

The visitor cannot quickly identify who the tool serves, what the first command does, and what outcome proves it worked.

Action

Show one clean path

Add a minimal fixture, command example, expected output, and non-goals section. The fastest buyer path is one honest run.

Strength

Native market signal

The tool converts README quality, licensing, contribution posture, examples, and handoff clarity into scored evidence.

What it checks

Repository presentation surface

README command path and outcome language.
License, contribution, authorship, and governance files.
Example fixtures that make evaluation concrete.
Public release language that avoids overclaiming capability.

Sample output

{
  "repo": "sample-release-tool",
  "score": 72,
  "status": "needs-polish",
  "blockers": [
    "No expected-output example",
    "README does not name buyer/user action"
  ],
  "next_actions": [
    "Add one fixture-backed demo",
    "Add non-goals and safety boundary",
    "Add evidence receipt link"
  ]
}

Commercial use

Small utility, direct value

For employers, this shows disciplined release thinking. For clients, it becomes a pre-release cleanup check before publishing internal tools, open-source utilities, or AI-assisted code drops.

Mission fit

AI output needs an edge check

AI can produce code faster than teams can assess the surrounding evidence. This tool focuses where code becomes a claim: documentation, examples, boundaries, and proof that the release is safe to evaluate.