sub-fixture

Resolve fixture call targeting to the correct package root for sub-fixtures.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill sub-fixture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sub-fixture
Source: https://github.com/usurobor/cnos/tree/main/schemas/fixtures/skill-frontmatter/valid/full/sub
Command: npx skills add https://github.com/usurobor/cnos --skill sub-fixture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This sub-fixture skill provides a stable anchor for test fixtures so that the full fixture's calls-target resolution can be validated in isolation.

Core Features & Use Cases

  • Fixture anchor: ensures sub-fixture calls resolve to the correct package root.
  • Integration testing aid: supports nested fixture compositions within a broader fixture suite.
  • Deterministic behavior: yields predictable resolution outcomes for test scenarios.

Quick Start

Use this sub-fixture to verify that fixture call targets resolve correctly within the parent fixture suite.

Frequently Asked Questions about sub-fixture

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

FAQPage Schema
How do I resolve fixture calls to the correct package root during integration testing?▼

To resolve fixture calls to the correct package root during integration testing, use a sub-fixture anchor to validate nested fixture compositions and ensure deterministic call targeting within your broader fixture suite.

What is a sub-fixture in the context of a nested fixture suite?▼

A sub-fixture is a stable anchor that allows a parent fixture's calls-target resolution to be validated in isolation, ensuring nested fixture scenarios yield predictable outcomes within an integration testing suite.

How do I validate nested fixture compositions for deterministic test outcomes?▼

You can validate nested fixture compositions by applying this fixture anchor, which ensures sub-fixture calls resolve to the correct package root and yields predictable resolution outcomes for your test scenarios.

Does this fixture resolution approach work with existing artifact and scope constraints?▼

Yes, this fixture resolution approach satisfies constraints on artifact_class, governing_question, scopes, and inputs/outputs as defined in the fixture suite metadata during integration testing.

When do I need to anchor sub-fixture calls during test resolution?▼

You need to anchor sub-fixture calls when validating isolated test resolutions within a parent fixture suite, specifically to ensure deterministic behavior and correct package root identification during integration testing.