arbe-pipeline-audit

Audit README pipeline diagrams against actual call paths to flag unnecessary wrapper functions.

Updated May 16, 2026
One-click install
npx skills add https://github.com/oskarrough/robots --skill arbe-pipeline-audit-oskarrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbe-pipeline-audit
Source: https://github.com/oskarrough/robots/tree/main/skills/pipeline-audit
Command: npx skills add https://github.com/oskarrough/robots --skill arbe-pipeline-audit-oskarrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate helper functions that were never earned — single-caller wrappers, same-args shims, and functions missing from the documented architecture. This Skill walks a README pipeline diagram against the real call path and flags every function that fails one of three smell tests, then decides each case interactively with the user. ## Core Features & Use Cases - Call-path tracing: Walks the call graph from a diagram's entry point to its terminal action, recording every function crossed and mapping each to a named diagram stage. - Three smell tests: Flags functions that are not in the diagram, have a single caller, or are same-args shims wrapping their callee with a thin transform. - Interactive verdicts: Presents candidates one at a time with a lean (remove, keep, promote, or reshape) so the user confirms or overrides each decision instead of rubber-stamping a batch list. - Use Case: Before a refactor sweep, run the audit on the create-file pipeline and get a reviewed list of wrappers to inline, stages to add to the README, and helpers worth keeping with a documented reason. ## Quick Start Ask the AI to run the pipeline audit on the create-file diagram in the README and walk you through each candidate function.

Frequently Asked Questions about arbe-pipeline-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find unnecessary wrapper functions in my codebase?▼

Trace the call path from a pipeline's entry point to its terminal action and apply three smell tests: not in the diagram, single caller, or same-args shim. A function failing two tests is almost certainly a wrapper in disguise that should be inlined.

How to audit code against an architecture diagram?▼

Pick one pipeline diagram, walk the call graph from its entry handler, and map every function crossed to a named stage. Functions with no matching stage are candidates to remove, keep with a documented reason, or promote into the diagram.

What is a same-args shim function?▼

A same-args shim is a function whose arguments match its only callee's arguments and whose body is a thin transform, such as converting null to a typed failure. The wrappee is the real function, so the shim should be inlined or folded into the callee.

When should I not run a pipeline audit?▼

Skip it when no README pipeline diagrams exist yet, during active feature work or incidents, and for single-file diffs. Establish diagrams first with an upstream diagramming skill, and use a diff-level review for small changes.

Should I run the audit in the same session that wrote the code?▼

No. Run it in a fresh conversation, because a session that just refactored the path already knows the wrappers and reads familiarity as a clean audit. Fresh context surfaces the functions the diagram is missing.