lane-check

Checks repos for forbidden cross-lane imports and reports violations with file, line, and RACI rule.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill lane-check-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lane-check
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/lane-check
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill lane-check-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a multi-repo agentic workflow, dev teams can silently import code across architectural lane boundaries, violating the separation rules defined in ADR-001. This Skill automates the audit so lane-creep is caught before a sprint accept instead of discovered later as tangled dependencies. ## Core Features & Use Cases - Lane-boundary linting: Runs lane-boundary-lint.sh against each repo's declared docs/architecture/lane-rules.txt and reports violations with file, line, lane, and the RACI rule broken. - Single-repo or fleet-wide audits: Check the current repo, a specified repo path, or fan out across every active project registered in .cto/projects.yaml with --all. - Actionable routing: Violations are routed to the owning dev team to either fix the import or open a CTO/ADR conversation to formally move the boundary. - Use Case: Before accepting a sprint, run the check across all active repos to confirm no team introduced a forbidden cross-lane dependency, then assign each violation to its owning team. ## Quick Start Ask the agent to run a lane check across all active project repos before the sprint accept.

Frequently Asked Questions about lane-check

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

FAQPage Schema
How do I check for forbidden cross-lane imports in a repo?

Run the lane check, which executes lane-boundary-lint.sh against the repo's docs/architecture/lane-rules.txt. It reports each violation with the file, line number, lane, and the RACI rule that was broken.

How do I audit lane boundaries across multiple repos at once?

Pass the --all flag to fan the lint out across every active project registered in .cto/projects.yaml. Each repo is checked against its own lane-rules.txt, and results are grouped per repository.

What does a lane violation report include?

Each violation includes the file and line number of the offending import, the lane it belongs to, and the RACI rule it breaks. The report is actionable so the owning dev team can fix the import or escalate a boundary change.

What should I do when a cross-lane dependency is legitimate?

Do not silently accept it. Either fix the import to respect the boundary, or open a CTO/ADR conversation to formally move the lane boundary so the dependency becomes legal under the architecture rules.

Does the lane check require a specific language or framework?

No. The lint is engine-independent and pattern-based, working off each repo's declared lane-rules.txt rather than parsing a specific language. It runs via a bash script, so any repo with the rules file can be checked.