agentleFS
Sign inStart free
tuana-vntuana-vn/system-reverse-engineer/.github/skills/runtime-binding-verification/SKILL.md

runtime-binding-verification

Skill0 starsChanged 2 months agoMITView on GitHub

Prove how an abstraction, interface, mode, or configured choice becomes the concrete runtime implementation actually used, including DI/bootstrap/factory/provider/registry and alternate branches.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    test-only bindings vs production bindings

    line 61
  2. Distinctive:

    Search for every implementation and every creation/registration path of the abstraction.

    line 67
  3. Distinctive:

    Do not conclude from one call site.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Runtime Binding Verification

Mission

Close the gap between:

"an implementation exists"

and:

"this implementation is actually selected under these runtime conditions"

Start From

One high-impact abstraction, selector, factory, client, repository, handler, or mode whose active implementation matters.

Trace

Trace both directions where needed:

startup/bootstrap
→ registration / DI / provider / registry
→ selector/factory
→ config/runtime state
→ concrete implementation
→ real caller/use

and:

runtime caller
→ abstraction
→ creation/lookup
→ concrete instance
→ boundary

Search

Inspect as applicable:

  • constructors and new
  • dependency injection annotations/config
  • service loaders/plugins
  • factories/providers/builders
  • registries/maps
  • startup/main/application initialization
  • reflection/class-name loading
  • configuration mode switches
  • test-only bindings vs production bindings
  • legacy/inactive implementations
  • fallback implementations

Counterexample Search

Search for every implementation and every creation/registration path of the abstraction.

Do not conclude from one call site.

Output

Create/update:

docs/reverse-engineering/runtime-binding/<scope>.md

Required table:

Scope/ConditionAbstractionBinding MechanismConcrete ImplementationConfig/Runtime InputActive EvidenceAlternate BindingVerdict

Verdict:

VERIFIED_ACTIVE
VERIFIED_ALTERNATE
INACTIVE_LEGACY
TEST_ONLY
UNRESOLVED

Promote only after counterexample search and scope check.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free