Skip to content

Releases

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 00:40
bbb12ed

Minor Changes

  • #44 67c41a6 Thanks @Paalt! - The review flow now detects mistake classes and hardens them instead of patching them again, and the feature-map join stops over-selecting journeys.

    • fix-the-class joins the toolkit (adapted from pstack's correct): after a correction the repo has seen before, or as a hardening pass, find the mistake classes from the repo's own record and make each impossible at the highest level that works — architecture, types, a check whose error names the fix, a test, prose last — proven red on a real past instance, with an AGENTS.md table of rules and what enforces them.
    • review-pr marks classes mechanically (Phase 4, after the arbiter): a finding gets classEvidence when it has several sites in the diff, cites a rule the rules table marks prose only or does not list, or matches a defect an archived review or an open review-debt issue already recorded. The report gains a class chip and a Classes card; the published review body lists the classes before the sections.
    • resolve-review hardens class findings instead of only patching them: every site fixed, then fix-the-class at the guard levels (types, check, test) proven red on the instance just fixed, a rules-table row added or raised, architecture moves handed back as their own PR, and every sibling left outside the branch's scope named by file:line. The ledger gains a Classes block.
    • The feature-map join narrows by symbol. A changed file listed by several features keeps a feature only when another of its changed Paths matched directly or one of its Paths references an export the diff changed; a file with no exports drives every feature that lists it (field: a three-file refactor of a shared helper selected eight journeys). Features set aside are recorded as not-affected; the Driven-features block gains that word.
    • Launch works from a fresh worktree. create-verify-skill requires Launch to name what a worktree lacks (gitignored env files, per-checkout deployments, caches) and the repo's own setup command that provides them; refresh re-audits it.
    • Contract tests pin the classEvidence field name, the rules-table heading, and the narrowing phrase across producers and consumers.
  • #47 2f92589 Thanks @Paalt! - The plugins are renamed hp-review-toolkit and hp-code-publish, and their home is now humanityplus.solutions/commons/plugins. The Claude directory listing the humanity-plus-* names were made for isn't happening, so the plugins are published through this repo's marketplace. If you installed either plugin, swap it:

    claude plugin uninstall humanity-plus-review@humanity-plus
    claude plugin marketplace update humanity-plus
    claude plugin install hp-review-toolkit@humanity-plus

    Do the same for humanity-plus-publish@humanity-plus → hp-code-publish@humanity-plus. If you are still on the names before those (review-toolkit@humanity-plus, code-publish@humanity-plus), uninstall those instead. Add --scope project (or local) to the uninstall if you installed there. If your settings list the plugins under enabledPlugins, rename those keys. Slash commands move too, for example /hp-review-toolkit:review-pr. The skills CLI lane is unchanged.

    The Review Toolkit's full guide moves from review-toolkit.html in this repo to its own page, and the READMEs link there. The toolkit README's "What it runs and sends" now covers the verify skill, which reviews and fixes on your own checkouts use to start your app, and interrogate, whose external seat (today Codex) sends its brief to that provider under your own login. The bundle READMEs go back to the two-step marketplace install.

Patch Changes

  • #46 0e81d10 Thanks @Paalt! - Gate selection proves coverage, and every lens has a materials recipe.

    • Pick gates from CI, and prove each one covers the changed files. The baseline and the fix phase take the gate set from the CI workflow, by name, never the nearest-sounding package script, and record which changed files each gate reaches — the tool's globs and the workflow's own path filters and job conditions, so a job that did not run covers nothing (field: a workspace lint passed while CI's lint:ci caught script formatting it never scanned). A green CI run still stands in for running the gates, never for that pairing; a changed file no gate covers is recorded as a hole in the review's limitations and the fixer's over-to-you list. Stated once in review-pr; resolve-review and review-fix cite it, and a contract test keeps the three in step and refuses any return to script-name discovery.
    • Per-lens materials recipe. review-pr states in one table what every lens, and a generalist carrying several lenses, is handed beyond the common set; the context bundle is fenced by section so a doc-heavy bundle costs the bug lenses nothing and a small review spawns mechanically.
    • Contract phrase checks match on whitespace-collapsed text; the strings an agent copies into a shell still must sit on one line.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 17:15
d59e1a0

Minor Changes

  • #38 1bb2a68 Thanks @Paalt! - New blast-radius lens in review-pr, for changes that ship to production. It names the one safety fact the change rests on, proves it as far as reading allows on an evidence ladder (asserted → documented → traced → command-settled → observed, the same names as verifiedBy), writes the probe that settles it by execution, walks the change's reach past grep (other readers of the same bytes, the library at its pinned version, the path production actually runs, timing, rollback), and reports what it cleared as first-class output. On your own checkout the orchestrator runs the probe, so the fact arrives proven or contradicted. The report leads with a Blast radius card, publish.ts puts the fact at the top of the GitHub review body, and resolve-review re-runs the probe after its fixes. Runs from the medium tier up; trivial and light diffs skip it. The method adapts the blast-radius skill in Lauren Tan's (poteto) MIT-licensed pstack, credited in the toolkit README.

  • #41 b5389a5 Thanks @Paalt! - New create-verify-skill skill: generates — or refreshes — a repo-local verify-<app> skill that drives the real app the way a user does (launch, doctor, personas, drive, evidence, cleanup) plus a feature map with one file per user-facing feature, its source Paths and the seeded Personas it needs, proven by an observable end state. The generator interviews the repo, writes the skill into the host's project skill directory, and drives one feature end to end before handing over; refresh mode runs source readers per feature and one live pass and leaves only proven corrections in the working tree (a PR when asked). Both modes run on your own checkout against a local or disposable instance. The toolkit consumes the skill by shape: review-pr runs experiment claims and the blast-radius probe through its recipes on owned checkouts, and resolve-review drives the features a review touched after its fixes land, with the outcome in the resolution ledger. The method adapts the create-verification-skill and maintain-verification-skill skills in Lauren Tan's (poteto) MIT-licensed pstack, credited in the toolkit README.

  • #40 fef7ba8 Thanks @Paalt! - New interrogate[=N] arg for review-pr: the pipeline's one offensive pass. N adversaries (default 2), each in its own scratch worktree, are briefed to break the change by running it — three focuses, inputs and boundaries / state and time / environment and integration, assigned round-robin — and a finding survives only when the orchestrator's rerun in a fresh worktree reproduces it; the repro command, patch, observed and expected output travel with the finding and render on its card. Adversaries execute code, so the arg is honored only on an owned checkout or under REVIEW.md's ## Trust. Runners are detected, never assumed: seats run on the host's subagents, and when the Codex CLI is on PATH one seat runs there so the adversaries span model families; with one family the report says diversity came from the briefs. An Interrogation card shows each seat's found / kept / dropped ledger and the interrogate-only findings. Off by default, like holistic. The method adapts the interrogate and arena skills in Lauren Tan's (poteto) MIT-licensed pstack, credited in the toolkit README.

Patch Changes

  • #43 5dcaca0 Thanks @Paalt! - Field round from a five-PR queue run. review-pr: a repeated mechanical substitution (the same literal, rename, or import swap in every hunk) takes the light tier however many files it touches, and the light-tier text now defers to the ladder row instead of restating it; when the conflict probe hits most of a PR's files and base replaced what the PR edits, the review asks whether the PR is superseded — goal met on base by reading and measurement — before planning any merge. The intent lens compares equivalence and duplication claims (keys, resolved values, exports) instead of accepting them. recap.ts emits a one-line classification-only block when no mapped primitive was touched, instead of an empty diagram and table. reset-workspace.sh leaves review-report/verify/ in place when it archives stale findings — evidence dirs are keyed by phase and SHA, and moving them dangled every link the findings recorded. A running verify instance and the review scripts no longer collide: the generator now mandates runtime state (pids, port, head, log, registered clients) in the git dir — $(git rev-parse --git-dir)/verify/, shared registrations one level up in the common dir — so review-report/verify/ holds evidence only; check-clean.sh refuses while those pids are alive and fails loudly, leaving the original where it names, instead of nesting review-report/review-report when a launch recreated the directory mid-check; a contract test pins the pid-file path across generator and script. Existing generated skills pick the layout up on their next refresh. create-verify-skill: identifiers a generated Launch derives from the checkout path are sanitized to the target's charset, Doctor prints them, and refresh mode re-reads Launch, Doctor, and Cleanup against the generator's contract so existing skills pick the rule up. Review-fix on this round added: a superseded verdict is always comment, never approve; the review-pr README defers to the ladder row and a contract test keeps the light-tier predicate stated once; the light generalist owes a substituted token the hidden-reader grep that blast-radius would have done at a higher tier.

v0.3.5

Choose a tag to compare

@github-actions github-actions released this 20 Oct 20:32
7d599f0

Patch Changes

  • #36 74a45c6 Thanks @Paalt! - Both plugins now link their directory listing to a setup guide at humanityplus.solutions/commons/plugins, which covers the REVIEW.md, convention docs, and primitives map the Review Toolkit reads, and the repo files Code Publish checks. The listings now declare their icons and link to support (GitHub issues) and a privacy notice stating that the plugins collect nothing. The plugin READMEs point to the same guide, and the Review Toolkit's setup list now includes the convention docs step it was missing.

v0.3.4

Choose a tag to compare

@github-actions github-actions released this 20 Oct 18:23
9caa4fa

Patch Changes

  • #34 955add9 Thanks @Paalt! - Rewrapped one sentence in the primitives lens so the plugin directory's security scan stops reading a line that began with set; as the shell builtin that dumps the environment. Lens behavior is unchanged.

v0.3.3

Choose a tag to compare

@github-actions github-actions released this 20 Oct 18:13
56cb25d

Patch Changes

  • #32 2376465 Thanks @Paalt! - Reworded a few docs, error messages, and the sample report so the directory's security scan stops reading the word "pass" as the pass password manager and the sample's STRIPE_SECRET_KEY as a credential the plugin reads. The skills' behavior is unchanged.

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 20 Oct 16:42
a1d57e6

Patch Changes

  • #29 1347b5f Thanks @Paalt! - Both plugins now ship an icon: the Humanity Plus leaf. The review toolkit guide links to Bun's install page instead of showing a download-and-run command, and both READMEs state that the skills never read a token or key.

  • #31 7e31583 Thanks @Paalt! - humanity-plus-publish gets its own icon, the Humanity Plus leaf with a publish badge, so the two plugins are easy to tell apart in the directory.

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 20 Oct 16:26
07efe40

Patch Changes

  • #27 945391e Thanks @Paalt! - Three lens definitions reworded in 0.3.0 had quietly narrowed what they check; they're restored to full breadth in our own phrasing. zombies Boundaries covers time edges again (expiry at the boundary, clock rollover, DST — not only timeouts), Many covers concurrency again (async interleaving and ordering races — not only parallel access), and triage's always-high rule covers any authentication (API keys and service-to-service auth included — not only user sign-in and sessions).

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 20 Oct 14:14
d614666

Minor Changes

  • #24 3d80f7f Thanks @Paalt! - The plugins are renamed for the Claude directory: review-toolkit is now humanity-plus-review and code-publish is now humanity-plus-publish. The old names stop resolving once you update the marketplace, so if you installed either plugin, swap it for the new name:

    claude plugin uninstall review-toolkit@humanity-plus
    claude plugin install humanity-plus-review@humanity-plus

    Do the same for code-publish@humanity-plus → humanity-plus-publish@humanity-plus, and add --scope project (or local) to the uninstall if you installed there. If your settings list the plugins under enabledPlugins, rename those keys rather than adding new ones. Slash commands move with the plugin, for example /humanity-plus-review:review-pr. The skills CLI lane is unchanged.

    Each bundle README now has a one-step install line, says the skills are built for Claude Code, and lists everything the skills run and send. A few lens instructions in review-pr (triage, preflight, first-five, zombies) are reworded without changing what they check.

Patch Changes

  • #26 6250553 Thanks @Paalt! - review-pr and resolve-review fixes, from a CodeRabbit review of a repo that vendored the skills:

    • A findings.json from an earlier commit no longer survives new commits on the same PR. reset-workspace.sh keeps it only when it describes the checked-out commit, and resolve-review stops and asks before editing from findings about different code (#19).
    • Finding text can no longer close the report's own containers to render a spoofed verdict outside its card (#20).
    • Copying REVIEW.example.md no longer opts you into running colleagues' PRs: the execution: collaborators line ships commented out (#21). If you copied the template before this release, check your REVIEW.md's ## Trust section.
    • check-clean.sh no longer runs the check when it can't move review-report/ aside (#22).
    • SKILL.md gives one rule for when the seams lens runs: whenever triage finds interfaces between areas (#23).

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 14 Sep 14:18
5a9e595

Minor Changes

  • #15 8cfe5f2 Thanks @Paalt! - Team/org reviews: repos can opt colleagues' PRs into execution trust (## Trust in REVIEW.md, execution: collaborators — collaborator-authored, same-repo-head PRs get baseline checks, experiments, and merged-tree gates in a disposable worktree), the seams lens traces migrated grants through every authorization consumer, skeptic verification can reframe a finding to the lesser defect that survives instead of discarding it, and resolve-review states reviewed-SHA vs current head and recommends a re-review after substantial security fixes. Publishing on private repos: publish.ts --pages owner/name hosts the HTML report via a Pages-publishing repo (Enterprise access-controlled Pages) and --recap puts the system-recap block in the review body for PRs whose description you don't own; the review footer timestamp is now human-readable (DD.MM.YYYY - HH:MM). create-pr includes the system-recap block at PR creation when a primitives map exists, and gains a retrofit mode that rewrites an existing PR's title and body to the same standard.

Patch Changes

  • #16 b9e1e8f Thanks @Paalt! - Report fix: the Dependencies (WARM) table no longer overflows its card. Long unbreakable content in the Notes column — 40-char commit SHAs, command strings in inline code, embedded markdown tables — used to set the column width, pushing the table past the card edge and crushing the Package column to one word per line. The table now uses fixed layout with proportional columns, and inline code and embedded tables wrap inside the Notes cell.

v0.1.1

Choose a tag to compare

@github-actions github-actions released this 27 Aug 12:25
ec11a78

Patch Changes

  • #12 6e983d7 Thanks @Paalt! - Midnight redesign (#11): the toolkit guide and the review report now share one visual language — near-black indigo-tinted surfaces, hairline borders, Inter + JetBrains Mono. The report renderer (render.ts, recap.ts) and the finding-style lens were updated to match, so reviews produced by review-pr pick up the new look.

  • #9 4b113c7 Thanks @Paalt! - Add a unified release pipeline with changesets. The version in package.json is now the repo's release version; scripts/sync-plugin-version.mjs stamps it into every skills/*/.claude-plugin/plugin.json, the release workflow maintains a version PR and tags a GitHub Release on merge, and CI fails PRs whose plugin versions drift out of sync. The README documents how each install lane receives updates.