Repository navigation
docs: align the forkctl skill and help with 0.0.37 (FRK-024) - #107
Merged
Merged
Conversation
A review of the bundled skill against the 0.0.37 binary found gaps. The skill said nothing about declared patch checks or the append, propose, and promote publish modes, which a fork with publish: propose depends on, and nothing about publish --set-default or the FORKCTL_<LONG> variables. The --check-at help named only NAME=patch, though the parser also takes stack, the default. Closes FRK-024
ReviewIncremental · 0 open
SummaryWhat these patches changeThe changes are documentation and help text only. The one Rust change in Help text (
|
| File | Status | + | − |
|---|---|---|---|
.changeset/skill-content.md |
added | +5 | −0 |
.ctl/operator/SKILL.md.jinja |
modified | +24 | −2 |
skills/forkctl/SKILL.md |
modified | +24 | −2 |
src/cli.rs |
modified | +4 | −4 |
tasks.yaml |
modified | +9 | −0 |
tests/snapshots/cli__usage_spec_is_the_mounted_fork_grammar.snap |
modified | +2 | −2 |
Open
No open findings.
History
| When | Pass | Open |
|---|---|---|
| 15 Oct 16:08 UTC | Incremental | 0 |
any-victor
added a commit
that referenced
this pull request
Oct 17, 2026
…113) #105, #107, and #110 closed FRK-023, FRK-024, and FRK-025. qctl's `close-from-git` moves the three rows to the archive. - `openspec archive bind-flags-to-environment` moves the change to `openspec/changes/archive/2026-10-17-bind-flags-to-environment/`. Its delta becomes the new `openspec/specs/cli-environment/spec.md`, whose placeholder Purpose is replaced with a real one. - The proposal's relative links gain one `../` for the deeper path, and every target resolves. - FRK-023's `plan` names the moved proposal. The pinned qctl refuses plan edits on archived rows, so this one path is edited by hand, as in earlier archives. `mise run q check` and `openspec validate --all --strict` pass. No code change, so no changeset.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The operator asked for every ctl skill to be reviewed against current behaviour. I checked forkctl's bundled skill against every command's
--helpfrom the published 0.0.37 binary, and against the source.Gaps found and fixed
-C,-g,--check-at,--clear-checks), although they gate refresh, finish, rebase, and both hooks.publish: proposedepends on theproposeandpromoteflow: never merge the proposal pull request, and promote from a clone whoseHEADtree matches the proposal. The skill now coversappendtoo, andpublish --set-default.FORKCTL_<LONG>variables beyondFORKCTL_MANIFEST.--check-athelp named onlyNAME=patch, though the parser takesstack|patch, withstackthe default. Both help strings and the usage snapshot are updated.Checked and correct
The command table, the
init,check,patch,operation,rebase,contract, andapiflags the skill names, themise xrecovery path, and--preview, which is ctl-core's visible alias of--dry-run. The installed instructions already covered all four topics above.Proof
On a Linux build host, the usage snapshot and both operator renders were regenerated, and
mise run verifypassed,operator_docsincluded. The hooks passed on the pushed commit. A patch changeset ships the help text change.Closes FRK-024