Name: xfi-release
Author: zotoio

Prompt file imported from zotoio/x-fidelity (.cursor/commands/xfi-release.md). Copyright stays with the author.

xfi-release

Prepare for an X-Fidelity release following the unified release workflow.

Instructions

This command uses:

Skill: Read and follow the xfi-release-workflow skill at .cursor/skills/xfi-release-workflow/SKILL.md
Subagents: Use xfi-testing-expert and xfi-docs-expert in parallel for pre-release checks

Workflow

Read the skill file for complete release process details
Run pre-release checks in parallel:
- xfi-testing-expert: Verify all tests pass
- xfi-docs-expert: Verify documentation is up to date

Execute release preparation:

# Run full test suite
yarn test

# Verify build succeeds
yarn build

# Check what would be released
yarn release:dry-run

Verify commit messages follow conventional format:
- feat: → Minor release (0.X.0)
- fix: → Patch release (0.0.X)
- BREAKING CHANGE: → Major release (X.0.0)
Create release commit using proper format

Release Checklist

Release Preparation:
- [ ] All tests pass: yarn test
- [ ] Build succeeds: yarn build
- [ ] Dry run reviewed: yarn release:dry-run
- [ ] Documentation updated
- [ ] Commit message follows conventional format
- [ ] No uncommitted changes

Commit Convention Reference

Release-Triggering Commits

Type	Version Bump	Example
`feat:`	Minor (0.X.0)	`feat: add new rule for React hooks`
`fix:`	Patch (0.0.X)	`fix: resolve AST parsing for arrow functions`
`perf:`	Patch	`perf: optimize file scanning`
`revert:`	Patch	`revert: undo breaking change`
`bump:`	Patch	`bump: update dependencies`
`BREAKING CHANGE:`	Major (X.0.0)	Include in commit body

Non-Release Commits

Type	Use For
`docs:`	Documentation changes
`style:`	Code formatting
`chore:`	Maintenance, tooling
`refactor:`	Code restructuring
`test:`	Adding or updating tests
`build:`	Build system changes
`ci:`	CI/CD changes

Release Commands

# Interactive commit creation
yarn commit

# Dry run to preview release
yarn release:dry-run

# Check current versions
cat packages/x-fidelity-cli/package.json | grep version
cat packages/x-fidelity-vscode/package.json | grep version

Post-Release Verification

# Verify npm package
npm view x-fidelity version

# Verify global install
npm install -g x-fidelity@latest
xfi --version

Key Files

.releaserc.json - semantic-release configuration
scripts/prepare-unified-release.js - Pre-publish version updates
scripts/publish-unified-release.js - Publish both packages
.github/workflows/release-unified.yml - GitHub Actions workflow
CHANGELOG.md - Auto-generated changelog

Install xfi-release and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# xfi-release Prepare for an X-Fidelity release following the unified release workflow. ## Instructions This command uses: - **Skill**: Read and follow the `xfi-release-workflow` skill at `.cursor/skills/xfi-release-workflow/SKILL.md` - **Subagents**: Use `xfi-testing-expert` and `xfi-docs-expert` in parallel for pre-release checks ## Workflow 1. **Read the skill file** for complete release process details 2. **Run pre-release checks in parallel**: - `xfi-testing-expert`: Verify all tests pass - `xfi-docs-expert`: Verify documentation is up to date 3. **Execute release preparation**: ```bash # Run full test suite yarn test # Verify build succeeds yarn build # Check what would be released yarn release:dry-run ``` 4. **Verify commit messages** follow conventional format: - `feat:` → Minor release (0.X.0) - `fix:` → Patch release (0.0.X) - `BREAKING CHANGE:` → Major release (X.0.0) 5. **Create release commit** using proper format ## Release Checklist ``` Release Preparation: - [ ] All tests pass: yarn test - [ ] Build succeeds: yarn build - [ ] Dry run reviewed: yarn release:dry-run - [ ] Documentation updated - [ ] Commit message follows conventional format - [ ] No uncommitted changes ``` ## Commit Convention Reference ### Release-Triggering Commits | Type | Version Bump | Example | |------|--------------|---------| | `feat:` | Minor (0.X.0) | `feat: add new rule for React hooks` | | `fix:` | Patch (0.0.X) | `fix: resolve AST parsing for arrow functions` | | `perf:` | Patch | `perf: optimize file scanning` | | `revert:` | Patch | `revert: undo breaking change` | | `bump:` | Patch | `bump: update dependencies` | | `BREAKING CHANGE:` | Major (X.0.0) | Include in commit body | ### Non-Release Commits | Type | Use For | |------|---------| | `docs:` | Documentation changes | | `style:` | Code formatting | | `chore:` | Maintenance, tooling | | `refactor:` | Code restructuring | | `test:` | Adding or updating tests | | `build:` | Build system changes | | `ci:` | CI/CD changes | ## Release Commands ```bash # Interactive commit creation yarn commit # Dry run to preview release yarn release:dry-run # Check current versions cat packages/x-fidelity-cli/package.json | grep version cat packages/x-fidelity-vscode/package.json | grep version ``` ## Post-Release Verification ```bash # Verify npm package npm view x-fidelity version # Verify global install npm install -g x-fidelity@latest xfi --version ``` ## Key Files - `.releaserc.json` - semantic-release configuration - `scripts/prepare-unified-release.js` - Pre-publish version updates - `scripts/publish-unified-release.js` - Publish both packages - `.github/workflows/release-unified.yml` - GitHub Actions workflow - `CHANGELOG.md` - Auto-generated changelog

{ "prompt": "# xfi-release\n\nPrepare for an X-Fidelity release following the unified release workflow.\n\n## Instructions\n\nThis command uses:\n- **Skill**: Read and follow the `xfi-release-workflow` skill at `.cursor/skills/xfi-release-workflow/SKILL.md`\n- **Subagents**: Use `xfi-testing-expert` and `xfi-docs-expert` in parallel for pre-release checks\n\n## Workflow\n\n1. **Read the skill file** for complete release process details\n\n2. **Run pre-release checks in parallel**:\n - `xfi-testing-expert`: Verify all tests pass\n - `xfi-docs-expert`: Verify documentation is up to date\n\n3. **Execute release preparation**:\n ```bash\n # Run full test suite\n yarn test\n \n # Verify build succeeds\n yarn build\n \n # Check what would be released\n yarn release:dry-run\n ```\n\n4. **Verify commit messages** follow conventional format:\n - `feat:` → Minor release (0.X.0)\n - `fix:` → Patch release (0.0.X)\n - `BREAKING CHANGE:` → Major release (X.0.0)\n\n5. **Create release commit** using proper format\n\n## Release Checklist\n\n```\nRelease Preparation:\n- [ ] All tests pass: yarn test\n- [ ] Build succeeds: yarn build\n- [ ] Dry run reviewed: yarn release:dry-run\n- [ ] Documentation updated\n- [ ] Commit message follows conventional format\n- [ ] No uncommitted changes\n```\n\n## Commit Convention Reference\n\n### Release-Triggering Commits\n\n| Type | Version Bump | Example |\n|------|--------------|---------|\n| `feat:` | Minor (0.X.0) | `feat: add new rule for React hooks` |\n| `fix:` | Patch (0.0.X) | `fix: resolve AST parsing for arrow functions` |\n| `perf:` | Patch | `perf: optimize file scanning` |\n| `revert:` | Patch | `revert: undo breaking change` |\n| `bump:` | Patch | `bump: update dependencies` |\n| `BREAKING CHANGE:` | Major (X.0.0) | Include in commit body |\n\n### Non-Release Commits\n\n| Type | Use For |\n|------|---------|\n| `docs:` | Documentation changes |\n| `style:` | Code formatting |\n| `chore:` | Maintenance, tooling |\n| `refactor:` | Code restructuring |\n| `test:` | Adding or updating tests |\n| `build:` | Build system changes |\n| `ci:` | CI/CD changes |\n\n## Release Commands\n\n```bash\n# Interactive commit creation\nyarn commit\n\n# Dry run to preview release\nyarn release:dry-run\n\n# Check current versions\ncat packages/x-fidelity-cli/package.json | grep version\ncat packages/x-fidelity-vscode/package.json | grep version\n```\n\n## Post-Release Verification\n\n```bash\n# Verify npm package\nnpm view x-fidelity version\n\n# Verify global install\nnpm install -g x-fidelity@latest\nxfi --version\n```\n\n## Key Files\n\n- `.releaserc.json` - semantic-release configuration\n- `scripts/prepare-unified-release.js` - Pre-publish version updates\n- `scripts/publish-unified-release.js` - Publish both packages\n- `.github/workflows/release-unified.yml` - GitHub Actions workflow\n- `CHANGELOG.md` - Auto-generated changelog", "variables": [], "notes": "Prepare for an X-Fidelity release following the unified release workflow.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zotoio/x-fidelity", "path": ".cursor/commands/xfi-release.md", "ref": "fd6cfd9335ecefc6f0a00b186f542de1a05cd7ad", "url": "https://github.com/zotoio/x-fidelity/blob/fd6cfd9335ecefc6f0a00b186f542de1a05cd7ad/.cursor/commands/xfi-release.md", "key": "zotoio/x-fidelity/.cursor/commands/xfi-release.md" } } }

xfi-release

About

xfi-release

Instructions

Workflow

Release Checklist

Commit Convention Reference

Release-Triggering Commits

Non-Release Commits

Release Commands

Post-Release Verification

Key Files

Install xfi-release and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews