fabric-test
Skill49 starsChanged 6 months agoMITView on GitHub
⚠️ Artifacts-only mode: When deploy_mode is artifacts_only, Mode 2 (Post-Deployment Validation) is NOT invoked — the pipeline runner handles structural validation deterministically. Mode 1 (Test Plan) runs normally in all modes. The runner pre-generates test-plan.md via test-plan-prefill.py before this skill is invoked. Your job: (1) verify each acceptance criterion maps to the correct items/waves from the architecture handoff, (2) add edge cases and expected results where missing, (3) replace every <!-- AGENT: FILL --> marker with real content. Set review_outcome:…
In this repository8 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- fabric-deploySkill
- fabric-designSkill
- fabric-discoverSkill
- fabric-documentSkill
- fabric-healSkill
- grill-with-docsSkill
- handoffSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If any finding is routed_to: engineer, also write remediation-log.md per the schema at …
- Distinctive: line 33
Never invent ACs not in the Architecture Handoff
- Distinctive: line 34
Never modify Fabric items — validate only
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
⚠️ Artifacts-only mode: When
deploy_modeisartifacts_only, Mode 2 (Post-Deployment Validation) is NOT invoked — the pipeline runner handles structural validation deterministically. Mode 1 (Test Plan) runs normally in all modes.
Fabric Testing & Validation (QA Role)
Mode 1: Architecture Review + Test Plan (Phase 2a)
The runner pre-generates test-plan.md via test-plan-prefill.py before this skill is invoked. Your job: (1) verify each acceptance criterion maps to the correct items/waves from the architecture handoff, (2) add edge cases and expected results where missing, (3) replace every <!-- AGENT: FILL --> marker with real content. Set review_outcome: approved (no red blockers) or concerns (has red).
Mode 2: Post-Deployment Validation (Phase 3)
For live workspace validation:
python .github/skills/fabric-test/scripts/validate-items.py _projects/[name]/docs/deployment-handoff.mdvalidate-items.py emits a manual validation checklist (it does not call the Fabric REST API). Follow the checklist from tool output. Write _projects/[name]/docs/validation-report.md with status: passed | partial | failed.
If any finding is routed_to: engineer, also write remediation-log.md per the schema at .github/skills/fabric-test/schemas/remediation-log.md.
Constraints
- Never invent ACs not in the Architecture Handoff
- Never modify Fabric items — validate only
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
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.

