I looked for the dependency-update skill in RabbitLabs/random-bunny on Forgejo (default branch) and in this repo’s default branch, but there is no .cursor/ / SKILL.md (or similar) checked in. Before I can write solid acceptance criteria, I need a few answers:

Source location — Where should I copy from? (Forgejo branch/SHA, GitHub URL, or paste the skill files in a comment.)
Target layout — Where should the skill live in vylbot-app? (e.g. .cursor/skills/<name>/SKILL.md or another path you use elsewhere.)
Adaptation vs verbatim — Copy as-is, or tailor for this repo (package manager, audit command, release/milestone process, breaking-change ticket workflow)?
Scope with #576 — Should this skill match the dependency-update issue template described in #576 (yarn audit → 0 vulns, non-breaking updates in-repo, breaking changes as separate tickets)?
Epic — Should this issue link to a parent epic/milestone beyond 3.6.0?

Once these are answered I’ll flesh out acceptance criteria and move the ticket to needs/estimate.

## Planning questions (`needs/criteria`) I looked for the dependency-update skill in `RabbitLabs/random-bunny` on Forgejo (default branch) and in this repo’s default branch, but there is no `.cursor/` / `SKILL.md` (or similar) checked in. Before I can write solid acceptance criteria, I need a few answers: 1. **Source location** — Where should I copy from? (Forgejo branch/SHA, GitHub URL, or paste the skill files in a comment.) 2. **Target layout** — Where should the skill live in `vylbot-app`? (e.g. `.cursor/skills/<name>/SKILL.md` or another path you use elsewhere.) 3. **Adaptation vs verbatim** — Copy as-is, or tailor for this repo (package manager, audit command, release/milestone process, breaking-change ticket workflow)? 4. **Scope with #576** — Should this skill match the dependency-update issue template described in #576 (`yarn audit` → 0 vulns, non-breaking updates in-repo, breaking changes as separate tickets)? 5. **Epic** — Should this issue link to a parent epic/milestone beyond 3.6.0? Once these are answered I’ll flesh out acceptance criteria and move the ticket to `needs/estimate`.

Smithy-bot removed their assignment

2026-10-07 12:07:53 +01:00

Vylpes was assigned by Smithy-bot

2026-10-07 12:07:53 +01:00

Vylpes commented

2026-10-07 12:18:51 +01:00

Author

Owner

@Smithy-bot wrote in #563 (comment):

Planning questions (needs/criteria)

I looked for the dependency-update skill in RabbitLabs/random-bunny on Forgejo (default branch) and in this repo’s default branch, but there is no .cursor/ / SKILL.md (or similar) checked in. Before I can write solid acceptance criteria, I need a few answers:
1. **Source location** — Where should I copy from? (Forgejo branch/SHA, GitHub URL, or paste the skill files in a comment.)

2. **Target layout** — Where should the skill live in `vylbot-app`? (e.g. `.cursor/skills/<name>/SKILL.md` or another path you use elsewhere.)

3. **Adaptation vs verbatim** — Copy as-is, or tailor for this repo (package manager, audit command, release/milestone process, breaking-change ticket workflow)?

4. **Scope with #576** — Should this skill match the dependency-update issue template described in #576 (`yarn audit` → 0 vulns, non-breaking updates in-repo, breaking changes as separate tickets)?

5. **Epic** — Should this issue link to a parent epic/milestone beyond 3.6.0?
Once these are answered I’ll flesh out acceptance criteria and move the ticket to needs/estimate.

Don't worry about the contents, I'll add it myself, just make criteria say about the existence of it here

@Smithy-bot wrote in https://git.vylpes.xyz/RabbitLabs/vylbot-app/issues/563#issuecomment-23230: > ## [](#planning-questions-needs-criteria)Planning questions (`needs/criteria`) > > I looked for the dependency-update skill in `RabbitLabs/random-bunny` on Forgejo (default branch) and in this repo’s default branch, but there is no `.cursor/` / `SKILL.md` (or similar) checked in. Before I can write solid acceptance criteria, I need a few answers: > > 1. **Source location** — Where should I copy from? (Forgejo branch/SHA, GitHub URL, or paste the skill files in a comment.) > > 2. **Target layout** — Where should the skill live in `vylbot-app`? (e.g. `.cursor/skills/<name>/SKILL.md` or another path you use elsewhere.) > > 3. **Adaptation vs verbatim** — Copy as-is, or tailor for this repo (package manager, audit command, release/milestone process, breaking-change ticket workflow)? > > 4. **Scope with #576** — Should this skill match the dependency-update issue template described in #576 (`yarn audit` → 0 vulns, non-breaking updates in-repo, breaking changes as separate tickets)? > > 5. **Epic** — Should this issue link to a parent epic/milestone beyond 3.6.0? > > > Once these are answered I’ll flesh out acceptance criteria and move the ticket to `needs/estimate`. Don't worry about the contents, I'll add it myself, just make criteria say about the existence of it here

Vylpes removed the

question

label

2026-10-07 12:18:56 +01:00

Vylpes removed their assignment

2026-10-07 12:19:05 +01:00

Smithy-bot was assigned by Vylpes

2026-10-07 12:19:05 +01:00

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

RabbitLabs/vylbot-app#563

No description provided.

Rows
Columns

Copy over dependency update skill from random-bunny repo #563

Acceptance Criteria

Subtasks

Notes

Planning questions (needs/criteria)

Planning questions (needs/criteria)

Planning questions (`needs/criteria`)

Planning questions (`needs/criteria`)