CLI Command
shiro validate
Validate workflow JSON structure and cross-check against CI configuration.
Usage
bash
shiro validate -workflow <path> [-ci <path>]Flags
| Flag | Required | Description |
|---|---|---|
| -workflow | Yes | Path to workflow JSON file |
| -ci | No | Path to CI config (.gitlab-ci.yml or .github/workflows/) |
Examples
Validate Workflow Only
bash
shiro validate -workflow .shiro/workflow.jsonValidate with GitLab CI
bash
shiro validate -workflow .shiro/workflow.json -ci .gitlab-ci.ymlValidate with GitHub Actions
bash
shiro validate -workflow .shiro/workflow.json -ci .github/workflows/deploy.ymlCI Checks
The --ci flag performs cross-checks to catch common misconfigurations:
GitLab CI:
- • Pause steps require when: manual resume job with needs: dependency
- • Jobs using -state-store gitlab must expose .shiro/ as artifact
- • Initial jobs should use -fresh flag, resume jobs should not
GitHub Actions:
- • Pause steps should use environment protection rules
- • -state-store gitlab is GitLab-specific — use filesystem with artifacts