• (b2c5531) Delete the stale copy of the worklane skill, and bump to 0.24.0

    Ghost released this 2026-08-23 12:26:57 +00:00 | 67 commits to master since this release

    .opencode/skill/worklane-kanban-skill/SKILL.md was 223 lines of the same
    document assets/SKILL.md holds, shipped by nothing and checked by no test.
    It drifted the way a copy nobody reads does: its frontmatter still called the
    skill worklane_kanban, its examples still used short flags, and it knew
    nothing about relate, campaign, chown, check or the four-status flow.

    It was not inert while it existed, and that was worth confirming rather than
    assuming. opencode debug skill listed it by path, so an agent working in
    this repo saw two worklane skills and could load either: the current one out
    of ~/.claude/skills or this one. After the delete the same command lists
    worklane, worklane-review and worklane-plan and nothing else of ours.

    The two agent files named it in their skill permission blocks,
    "worklane_kanban": "allow", an id only the deleted file defined, so the
    permission granted access to nothing. Repointed at worklane, which is the
    surviving document and what the grant meant. The files themselves stay: they
    are the user's, and reviewing-agent.md is the prior art assets/REVIEW.md
    grew out of. Neither was given worklane-review or worklane-plan, which
    would be redesigning somebody else's agent rather than fixing a dead id.

    .opencode/skill/testing-skill is untouched for the same reason. It is not a
    copy of anything this repo ships.

    8cc254c fixed the add example in the file this deletes, and it is moot rather
    than reopened, recorded in a comment there. The fix was real: the example did
    pass -t where -g was meant, gave -p three bare positionals, and clap
    did reject it with exit 2. Nothing carries over, because assets/SKILL.md
    never had either defect. Its examples are long flags throughout, one value
    per flag, and it carries no "(or --due)" filler. Checked against the file.

    AGENTS.md now says the surviving document is the only one and names this copy
    as what happened last time, since the rule on its own does not say why it is
    there.

    The bump is the body of work's, not this commit's: install-tool in 11145b2
    is the new command, and one bump on the last commit is what this tree does
    when work spans several.

    Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

    Downloads