chore(deps): Bump rollup from 4.57.1 to 4.59.0 in /web#34
Merged
Conversation
Bumps [rollup](https://github.com/rollup/rollup) from 4.57.1 to 4.59.0. - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v4.57.1...v4.59.0) --- updated-dependencies: - dependency-name: rollup dependency-version: 4.59.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
spboyer
added a commit
that referenced
this pull request
Mar 3, 2026
E2 sensei engine (#32, #33) shipped but SKILL.md still listed `waza dev` as "coming soon". Updated documentation to reflect implemented features. ## Changes **Help text block** - Added DEV FLAGS section: `--target`, `--max-iterations`, `--auto` - Updated command summary to include `[skill-path]` argument **waza dev command section** - Usage examples for scoring workflows - Compliance levels: Low → Medium → Medium-High → High with progression criteria - Scoring checks: description length (150+ chars, 1024 max), trigger phrases, anti-trigger phrases, routing clarity markers, token budget (500 soft / 5000 hard) **Future features section** - Marked trigger accuracy tests (#36), `--skip-integration` (#37), `--fast` (#38), improvement suggestions engine (#34) as "Coming Soon" ```bash # Score and improve to high compliance waza dev skills/my-skill --target high # Auto-apply without prompts waza dev skills/my-skill --auto --max-iterations 3 ``` Current state: waza skill at High compliance (638 chars, 13 triggers, 3 anti-triggers), 2097 tokens. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>[E5] Update SKILL.md with sensei engine features when E2 completes</issue_title> > <issue_description>The waza SKILL.md (#52) was created with `waza dev` listed as 'coming soon'. Once Charles completes E2 (#32-38), update the SKILL.md to: > - Document `waza dev` command usage > - Add compliance scoring examples > - Add trigger accuracy test examples > - Update the help text block > > Blocked on: spboyer/waza#33, spboyer/waza#32</issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > <comment_new><author>@spboyer</author><body> > @copilot Please pick up this issue. Here's the scope: > > ## What's ready to document (blockers spboyer/waza#32 and spboyer/waza#33 are closed) > > 1. **`waza dev` command usage** — The sensei dev loop is implemented. Document the command, its flags (`--verbose`, `--target-score`, `--max-iterations`), and a usage example in the SKILL.md. > > 2. **Compliance scoring** — Document how compliance scoring works (the scoring system from spboyer/waza#33 is merged). > > ## What's still 'coming soon' (keep as placeholders) > > - Trigger accuracy tests (#36 — still open) > - `--skip-integration` flag (#37 — still open) > - `--fast` flag (#38 — still open) > - Improvement suggestions engine (#34 — still open) > > ## Files to update > - `skills/waza/SKILL.md` — the main SKILL.md for the waza skill > > Read the existing SKILL.md first, then update the sections that reference `waza dev` as 'coming soon' with actual documentation. Keep the token count reasonable (under 500 tokens for the SKILL.md frontmatter+body).</body></comment_new> > </comments> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Fixes spboyer/waza#93 <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: spboyer <7681382+spboyer@users.noreply.github.com>
spboyer
pushed a commit
that referenced
this pull request
Mar 3, 2026
This PR adds a new Copilot-powered suggestion mode to `waza dev` (closes #34). In this mode, waza asks an LLM to write suggestions for improving a skill's trigger accuracy considering its trigger tests, if any. ### Example usage ``` $ waza dev --copilot --model gpt-5.3-codex # Skill Selection Suggestions These suggestions were written by `gpt-5.3-codex` using 4 prompt example(s) from `trigger_tests.yaml`. ## Skill - Name: `test-skill` - Path: `skills/test-skill/SKILL.md` - Tokens: 318 ## Suggestions 1. Replace the description with a scoped purpose line, matey: `**UTILITY SKILL** - Give safe, step-by-step help for opening stuck pickle jars 🥒 2. Add a `USE FOR:` block with broader trigger phrases: ... 3. Add a `DO NOT USE FOR:` block covering unrelated asks: ... 4. Add an explicit trigger rule in description: ... 5. Add a disambiguation line: “Do not trigger on figurative ‘in a pickle’ unless jar-opening help is requested”. 6. Add `INVOKES:` and `FOR SINGLE OPERATIONS:` lines, e.g., ... ``` #### What was added - Added non-interactive `--copilot` mode to `waza dev` that generates a markdown report instead of editing `SKILL.md`. - Added `--model` flag (default: `claude-sonnet-4-20250514`) for selecting the Copilot model in report mode. - Added Copilot suggestion prompt template at `cmd/waza/dev/suggest_prompt.md`. - Reusable spinner package at `internal/spinner/spinner.go` with: - Animated terminal spinner output. - Proper line clearing on stop. - `sync.Once` guard to make `stop()` safe to call multiple times. #### Behavior and UX - `--copilot` mode: - Reads and analyzes `SKILL.md`. - Attempts to discover and include trigger examples from workspace `evals/<skill>/trigger_tests.yaml`. - Calls Copilot once and prints a markdown report with skill metadata and actionable suggestions. - Does **not** mutate `SKILL.md`. - Flag validation: - `--target`, `--max-iterations`, and `--auto` are rejected when `--copilot` is set. - `--model` is rejected unless `--copilot` is set. #### Refactoring and internal improvements - Extended `devConfig` with context/model/copilot/error-stream fields. - Extracted iterative frontmatter suggestion selection into `collectFrontmatterSuggestions`, simplifying `improve`. - Added test hooks for engine and spinner injection in `cmd/waza/dev/copilot.go`. #### Tests and docs - Added comprehensive tests in `cmd/waza/dev/copilot_test.go` covering: - Flag defaults and validation. - Spinner invocation. - No-mutation guarantee. - Custom model display. - Engine error and empty-output handling. - Trigger prompt loading (including fallback/warning behavior). - Command context cancellation behavior. - Updated `README.md` to document new `waza dev --copilot` workflow and flag semantics. ## Net Effect - `waza dev` now supports a safe, report-only Copilot workflow for frontmatter/routing-quality improvements. - Spinner behavior is centralized and reusable, reducing duplicated terminal UI logic. - Coverage is improved with focused tests around new Copilot mode behavior and edge cases.
spboyer
pushed a commit
that referenced
this pull request
Mar 3, 2026
Bumps [rollup](https://github.com/rollup/rollup) from 4.57.1 to 4.59.0. - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v4.57.1...v4.59.0) --- updated-dependencies: - dependency-name: rollup dependency-version: 4.59.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Bumps rollup from 4.57.1 to 4.59.0.
Release notes
Sourced from rollup's releases.
Changelog
Sourced from rollup's changelog.
Commits
ae846954.59.0b39616eUpdate audit-resolvec60770dValidate bundle stays within output dir (#6275)33f39c14.58.0b61c408forward NO_SIDE_EFFECTS annotations to function expressions in variable decla...7f00689Extend agent instructionse7b2b85chore(deps): lock file maintenance (#6270)2aa5da9fix(deps): update minor/patch updates (#6267)4319837chore(deps): update dependency lru-cache to v11 (#6269)c3b6b4bchore(deps): update dependency eslint-plugin-unicorn to v63 (#6268)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.