run: an outdated committed skill tree runs under a newer CLI with a one-line warning and no record
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
The warning is emitted in src/commands/sync.ts near line 1026, and the run log's sequantVersion field (#1198) is where the skill tree version would be recorded beside the CLI version. Start by reading the outdated-skills check and the run log writer, then check whether a --strict-skills flag fits the existing run options. Done means the header prints both versions when they differ, the log stores the skill tree version, and a test covers the mismatch case.
Written by the indexing model from the issue text.
Description
What happens
sequant run on a repo whose committed .claude/skills tree is from an older sequant prints
! Skills are outdated (2.18.0 → 2.20.0)
(src/commands/sync.ts:1026) and runs the phases with the old tree. The warning is one stdout line; the summary table and, as far as I checked, the run log do not carry the skill tree's version.
Evidence (sequant 2.20.0 at 31c6f8bd, 22 F runs on a mirror of matcha-maps whose committed tree is 2.18.0, 2026-11-01 to 2026-11-03)
22 of 22 run stdouts carry the line ! Skills are outdated (2.18.0 → 2.20.0) (grep -l over the smoke, pilot and batch runs), followed by Phases spec → exec → qa and Quality loop enabled (max 3 iterations). All 22 runs proceeded on the 2.18.0 skills. The run log's sequantVersion (#1198) says 2.20.0, which is the CLI, not the skills that ran.
Ask
- Record the skill tree's version in the run log beside
sequantVersion, and print both in the header when they differ. - A
--strict-skillsflag (orrun.strictSkills) that refuses to start on a mismatch, for benchmark and CI use. - Optional: when the mismatch is a minor version, offer
sequant syncin the warning's text.
Why it matters
A run that says "2.20.0" in its log executed 2.18.0's prompts. Anyone comparing runs across repos, or against a changelog, is comparing skill trees they cannot see.
From a private replay study of sequant on our own repos; raw runs are not public. Filed by the owner.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 84
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sequant-io/sequant
-
graph-2026-11-simplify
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1650 ·
Maintainers usually reply within 1 day
-
run: --phases does not suppress the UI-label test phase (determinePhasesForIssue adds it to an explicit list)Possibly taken @admarble claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sequant-io/sequant#1601 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sequant-io/sequant#1582 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
sequant-io/sequant#1381 ·
Maintainers usually reply within 1 day
All issues in sequant-io/sequant
Similar issues
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tensorflow/tfjs#8754 ·
-
tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 83/100
BraveOPotato/NoSignups#2348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#12784 ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 1 day