Skip to content

fix: use @paralleldrive/cuid2 in task requirements for consistency #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ericelliott merged 2 commits into from
Feb 19, 2026
Merged

fix: use @paralleldrive/cuid2 in task requirements for consistency #99

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
197de7a
Initial plan
Copilot Feb 19, 2026
497733d
fix: use @paralleldrive/cuid2 in task requirements for consistency
Copilot Feb 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tasks/npx-aidd-create-epic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Minimal fast-running scaffold at `ai/scaffolds/scaffold-example` used as the e2e

**Requirements**:
- Given the scaffold runs, should initialize a new npm project in `<folder>`
- Given the scaffold runs, should install `riteway`, `vitest`, `@playwright/test`, `error-causes`, `cuid2`, and `release-it` at `@latest`
- Given the scaffold runs, should install `riteway`, `vitest`, `@playwright/test`, `error-causes`, `@paralleldrive/cuid2`, and `release-it` at `@latest`
- Given the scaffold runs, should configure `scripts.test` as `vitest run`
- Given the scaffold runs, should configure `scripts.release` as `release-it` so the generated project can publish GitHub releases
- Given the scaffold runs, should leave a working project where `npm test` can be invoked
Expand Down