contributing
Installation
SKILL.md
Fabric Contribution Flow Skill
This skill defines the end-to-end workflow for contributing to Cloud Foundation Fabric. It supports two entry modes:
- Mode A: Issue Triage & Bug Fix: You are addressing an assigned or reported GitHub Issue. Start at Step 1.
- Mode B: Proactive Development & PR Prep: You are actively building a feature, refactoring code, or preparing an existing branch for a Pull Request. Jump directly to the Design Sign-off Gate before Step 2.
If it is unclear which mode applies, ask the user before proceeding.
Human-in-the-Loop Gates
Gate on steps that are hard to reverse, costly, or where your judgment is likely to diverge from a maintainer's. Keep mechanical, reversible steps (linting, tests, doc and inventory regeneration) autonomous. Gates are blocking: if you are running non-interactively and cannot get an answer, stop — never assume approval.
| Gate | When | What the human decides |
|---|---|---|
| Triage Disposition | End of Step 1 (Mode A) | Whether the issue is in scope and worth pursuing: proceed, reject, or escalate. |
| Design Sign-off | Before Step 2 | Approves the proposed design and scope. Mandatory for new features and interface changes; skippable for trivial fixes where the design is self-evident. |
| E2E Opt-in | Step 5 | Whether to run live cloud verification. Providing a sandbox project ID is the consent to deploy to it. |
| Behavioral Verification Opt-in | Step 5, after read-back verification | Whether to also verify runtime behavior of the deployed resources, given the described extra time and cost. |
| PR Approval | Step 6 | Reviews the final sanitized PR body before submission. |