Audit

Skill lubochka/xiigen-mvp-engine/.agents/skills/audit

Self-building AI code generation engine that generates application flows instead of implementing them. AGPL-3.0.

Install

npx -y skills add lubochka/xiigen-mvp-engine --skill audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, as published. Nobody here has run it

API Shape Verification Skill

For every import in a planned test file, verifies the export shape, parameter types, and return type from the actual source file before any test code is written. Front-loads API discovery to G0 instead of find-and-fix during execution.

When to Invoke

At G0, after infrastructure discovery identifies the source files to be imported
Before writing any test file that imports from engine source files
After any session that had WF discovery rate > 120% (indicates API assumptions were wrong)

Verification Protocol

For each planned import:

# Step 1: Find the export — do NOT assume function vs const
grep -n "export.*SymbolName\|SymbolName" source_file.ts | head -10

# Step 2: For methods/functions — confirm param order and types
grep -n "async SymbolName\|SymbolName(" source_file.ts | head -5

# Step 3: For getters — confirm getter vs method
grep -n "get SymbolName\b" source_file.ts | head -5

Verification Table

Produce this table before writing any test code:

Symbol	Source File	Export Shape	Params	Return Type	Notes	Verified
`FlowGenerator`	`engine/flow-generator.ts`	class	`{aiProvider}`	instance	constructor options	✅
`generate`	method on FlowGenerator	async method	`(contract, tenantId)`	`Promise<DataProcessResult>`	order matters	✅
`generationHistory`	method on FlowGenerator	getter	none	`Array<Record<string,unknown>>`	NOT a method call	✅
`createT44Contract`	`engine-contracts/sample-contracts.ts`	?	`()`	`EngineContract`	grep to confirm	⬜

Rules

Never use ^export function — misses export const, export class, default exports, arrow functions
Use grep "export.*SymbolName" without anchors to catch all export forms
If symbol not found in the named file: search the barrel index (index.ts) for re-exports
If shape differs from plan: create a FIX-AT-WRITE entry with the real shape
If symbol not found at all: STOP — do not write the test, report to Luba
Complete the full verification table before writing the first line of test code

XIIGen Discovery History

Session	WF Fixes	Type	Root Cause
S2 WF-1	`useFlowDefinition` initial state	API assumption	Plan assumed eager load
S2 WF-2	`useModelPerformance` import path	API assumption	Wrong file extension
S3 WF-2	`getQueueDepth` sync vs async	API assumption	Plan assumed async
S3 WF-3	`ElasticsearchProvider` constructor	API assumption	Wrong second arg type
S3 WF-5	`dequeue` second param type	API assumption	Plan used string not number
S3 WF-6	`getSecret` return envelope	API assumption	Plan accessed wrong field

All 6 were API shape discoveries. This skill would have caught them at G0.