Files
orca/config/scripts/orca-cli-skill-guidance.test.mjs
T
Jinjing a1cbb31f27 Clarify worktree lineage and handoff rules in skills and CLI help (#5892)
- Explain that `--no-parent` only controls Orca lineage, not the Git
  base branch, and detail how to target independent top-level work.
- Define full handoffs as ownership transfer and forbid the use of
  orchestration dispatch injection for them.
- Update CLI help text for `orca worktree create` to reflect the
  lineage and base-branch guidance.
- Add tests to verify that these guidance patterns exist in the skill
  markdown files.
2026-06-20 01:51:35 -07:00

18 lines
746 B
JavaScript

import { readFileSync } from 'node:fs'
import { dirname, join, resolve } from 'node:path'
import { fileURLToPath } from 'node:url'
import { describe, expect, it } from 'vitest'
const projectDir = resolve(dirname(fileURLToPath(import.meta.url)), '../..')
const skillPath = join(projectDir, 'skills', 'orca-cli', 'SKILL.md')
describe('orca CLI skill guidance', () => {
it('keeps independent worktree lineage separate from Git base selection', () => {
const skill = readFileSync(skillPath, 'utf8')
expect(skill).toContain('`--no-parent` only controls Orca lineage')
expect(skill).toContain('omit `--base-branch` so Orca uses the repo default base')
expect(skill).toContain('Never base it on the current feature branch')
})
})