Skip to content

Releases

v0.19.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 20:56
  • Docs: README mentions the reviewer's extra commands. The review-gate step of the README
    says the reviewer is read-only and that a project can allow more commands for it in
    .youtrack-task/reviewer-commands, linking docs/configuration.md#letting-the-reviewer-run-more;
    the Configuration entry of the docs table names them. No behaviour change.
  • tests/skill-text.sh checks that the README links that section and that the heading exists.

v0.19.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 20:31
55bcb31
  • Reviewer: an allowed way to verify, still read-only. The ticket-reviewer guard
    (hooks/guard-subagent) now also allows swift test, swift build, go build ./...,
    golangci-lint run and scripts/*test*. Options that write or steer a build (--fix,
    -o, -toolexec, -ldflags, -Xswiftc, --package-path) stay rejected.
  • New config key reviewer_commands and a per-project file
    .youtrack-task/reviewer-commands (one command per line, # comments): extra
    commands the reviewer may run, each matched exactly (whole command, no regex, no
    prefix). The project file is read from the base branch with git show, never from the
    branch under review, so a branch cannot allow commands for its own review. See
    reference/reviewer-allowlist.md and docs/configuration.md.
  • A rejected reviewer command is no longer a code finding. The hook marks it
    [blocked-by-guard]; the reviewer reports BLOCKED_BY_GUARD and the review gate returns
    BLOCKED without a fix round, without a stamp, listing the commands and how to allow them.
    Before, "build, lint or CI not checkable" ended as CHANGES_REQUESTED.
  • The base branch of .youtrack-task/reviewer-commands is resolved from full ref names
    (refs/remotes/origin/HEAD, refs/remotes/origin/main|master, refs/heads/main|master)
    and read by commit id, so a tag named main or origin/main cannot shadow it. The worker
    guard also denies git symbolic-ref writes, git remote set-head, git replace,
    git fetch / git pull into refs (also --refmap), git branch --force/--move/--copy
    (also abbreviated), git checkout -B, git switch -C and git worktree add -B, checked on the command with
    its quote characters removed (and git -C <dir> normalised first, the dir read as a whole shell word: quoted, escaped or plain) so quoting an argument
    does not hide it; the lookups ignore replace refs.
  • read-config resolves reviewer_commands (REVIEWER_COMMANDS, entries joined with ;).
    Tests cover the new built-ins, both extra sources and the self-allowing branch.

v0.18.5

Choose a tag to compare

@github-actions github-actions released this 12 Nov 17:05
16c5c9d
  • Docs: not just a Claude Code plugin. The README header, tagline and badge now say
    the tool also runs in Cursor, GitHub Copilot, Codex CLI and other MCP-capable agents.
    The install step offers four routes (Claude Code plugin, Agensi, Product Hunt, other agents), and
    the README shows the Product Hunt badge (in the header and in the install table) and links
    the Agensi listing. The agent setup
    moved to the new docs/other-agents.md (MCP settings per agent, what differs outside
    Claude Code, building the Agensi package).

  • tests/skill-text.sh checks that the README links docs/other-agents.md, the Agensi
    listing and the Product Hunt badge, and that the header names other agents.

  • Docs: shorter, scannable README. README.md is now the entry point only: what
    the plugin does, a quick start, the task flow, a command cheat sheet and
    links. The detail moved, unchanged in substance, to docs/usage.md,
    docs/batch.md, docs/configuration.md and docs/troubleshooting.md (the
    troubleshooting table is grouped by topic).

  • tests/skill-text.sh reads the Config overrides section and the fixed-ladder
    statement from docs/, and checks that the README links every docs page.

v0.18.4

Choose a tag to compare

@github-actions github-actions released this 12 Nov 03:07
  • Docs: end-to-end example. New skills/youtrack-task/examples/full-lifecycle.md
    follows one issue from new through pickup, plan, --implement, pr and done,
    with the state change and comment each step writes. The README's The full
    lifecycle
    section links to it, and SPEC.md lists it in the file tree.
  • tests/skill-text.sh checks that the example exists, covers every step, and is
    referenced from README.md and SPEC.md.

v0.18.3

Choose a tag to compare

@github-actions github-actions released this 11 Nov 19:18
  • Fix: no improvised go-ahead question before the pickup. The rule "the
    invocation authorizes the pickup" lived only in step 4, so a wrong input in step 1
    (a mistyped project key such as BUS-187) made the model ask "Shall I continue
    with …?"
    even with confirm_branch_name = false. It is now a Guardrail ("No
    unlisted confirmation questions"), and step 1 stops on an ID that does not exist,
    names it and the likely intended <PROJECT>-<number>, and asks nothing.
  • → Branch: <name> is printed in both rows of the step 4 table, so the applied
    setting is always visible.
  • reference/branching.md defers to the step 4 table. Its unconditional wording
    ("proceed only after the user has seen it") contradicted confirm_branch_name = false.
  • tests/skill-text.sh checks the new rules; the SKILL.md line limit is 390.

v0.18.2

Choose a tag to compare

@github-actions github-actions released this 11 Nov 08:52
  • Config limits documented. config.example.toml and the README say that arrays
    must be written on one line; a multi-line array falls back to the default.
  • State ladder documented as fixed. reference/writeback.md, the README and
    SPEC.md state that only the state names are configurable, not the order.
  • CONTRIBUTING.md has the tag step of the change checklist.
  • README Config overrides names list_query, local_plan_copy and
    default_new_type.

v0.18.1

Choose a tag to compare

@github-actions github-actions released this 11 Nov 08:47
  • One definition per rule. The language rule is worded only in SKILL.md;
    writeback.md, issue-template.md, batch.md and superpowers.md point to it.
    confirm_branch_name / confirm_pr are decided by the tables in SKILL.md step 4
    and reference/pr.md step 4, and the never-force / never--D / dirty-worktree
    limits by the Guardrails; branching.md, subcommands.md and batch.md refer
    to them. No behaviour changed.
  • Confirm tables lead with the effective value (flag over config) instead of a
    condition in the header cell.
  • review.md is the runtime procedure only. The stamp contract and the hook
    internals moved to SPEC.md.
  • Examples match the spec: new shows Context and Scope, pr shows the review
    gate, pickup shows the branch line, the plan comment, --implement, the review
    gate and the completion comment.
  • scripts-fallback.md is marked as the path for a missing scripts/ only and
    names what it cannot resolve ([type_prefix], array keys).
  • tests/skill-text.sh checks the above.

v0.18.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 08:23
  • SKILL.md loads only what the call needs. It shrank from 813 to 372 lines:
    new, pr, the small sub-commands (testing, done, log, comment, link,
    worktree), the project-resolution procedure, the "scripts missing" fallback
    and the workspace set-up of the primary flow moved to reference/new.md,
    pr.md, subcommands.md, projects.md, scripts-fallback.md and
    pickup.md; all points to batch.md. Guardrails, Language, Config, Issue IDs,
    the dispatch table and the primary flow stay in SKILL.md. Text moved, rules did
    not change.
  • Hard read instructions. Every dispatch row names its reference file with
    "read reference/X.md before acting"; pr and all carry it in the table.
  • Shorter description, triggers only. 355 characters instead of about 590; no
    workflow summary, with triggers for a pasted issue URL or ID, booking time,
    status changes, attaching a PR and batch runs.
  • tests/skill-text.sh checks the size limit, the description, that every
    dispatch row names an existing reference file, that the Guardrails stay in
    SKILL.md, and that the moved sections are gone from it.

v0.17.2

Choose a tag to compare

@github-actions github-actions released this 11 Nov 07:59
97a3c1b
  • New logo. A dark metallic tile with the branch-and-check mark in front of two
    pink shapes, on a fully transparent background. assets/logo.svg is the source;
    assets/logo.png (512 px, RGBA) is exported from it and replaces the previous
    logo in the README header.

v0.17.1

Choose a tag to compare

@github-actions github-actions released this 11 Nov 07:45
  • Fix: one issue-ID regex. ISSUE_ID_RE ([A-Z][A-Z0-9_]*-[0-9]+) is defined
    once in SKILL.md ("Issue IDs") and is the only form in the skill, reference/,
    SPEC, README, review-stamp and hooks/require-review. Before, a branch like
    fix/P2X-5-foo read as X-5 in the sub-commands, so a comment or state change
    could land on the wrong issue. New tests/skill-text.sh keeps the forms
    identical; P2X-5 cases added to tests/review-stamp.sh and
    tests/require-review.sh.
  • Fix: scripts are called by absolute path. <skill-dir> (${CLAUDE_SKILL_DIR}
    in Claude Code) is defined once; scripts run as <skill-dir>/scripts/<name>
    with the target repo as working directory instead of "from this skill's
    scripts/ directory". Step 0 checks test -x <skill-dir>/scripts/read-config
    (SCRIPTS=present|missing) to decide on the plain-git fallback.
  • Fix: pr order. Checks → clean tree (commit / stash, asked once) → review
    gate or waiver → diffstat and confirmation → push → PR → state change → comment.
    The comment's , moved to Testing. suffix now reflects whether the state really
    changed. review_before_pr = never and --no-review both record a SKIPPED
    waiver (only the flag asks first).
  • Fix: first-token parsing. For comment / log / pr / link / testing /
    done a leading token matching the ID form is the issue, anything else is text
    and the issue comes from the branch.
  • Fix: resume. On existing-worktree / existing-branch the skill checks the
    comments for the pickup and plan headings and only skips steps 5 and 7 when
    those comments exist.
  • Fix: bare issue numbers read the issue before asking for confirmation, so
    the question shows the title.
  • Removed the "dominant project prefix" guess; only "Resolving a project"
    applies.
  • Changed: step 8 needs --implement. The "proceed now?" question is gone.
    Without the flag the flow ends after the plan write-back and prints the command
    to continue.
  • Changed: the local plan copy is always English (a git artifact); the
    YouTrack comment follows the issue's language.
  • Docs: confirm_pr applies to pr only (all always asks its batch
    confirmation); worktrees are entered with EnterWorktree or per-call working
    directories instead of cd; worktrees.md describes done's automatic
    sweep; the completion comment is described one way everywhere.