genvid-dev

Explores a problem space, understands current state, and produces a requirements document. Reads existing code, identifies constraints, and surfaces touch points without proposing solutions. Use before designing — when the user asks for analysis, when a planning task starts, or when requirements aren't yet clear.

Read-only. Fetches a project's bug corpus via its declared tracker commands and returns one structured triage report — duplicate clusters, overlaps, dependencies, split candidates, and per-bug field/label/priority/language proposals. Proposes changes; never writes. Use as the exploration phase of the triage-bugs skill.

Reviews code for quality, security, project conventions, and documentation freshness. Produces feedback organized by priority (critical / warnings / suggestions / what's good) with specific file paths and line numbers. Use after writing or modifying code, before opening a PR, or when explicitly asked for a review.

From a requirements document, proposes a concrete design with 2-3 options, a friction audit, a footprint audit (for drop-X/preserve-Y directives), library-vs-custom evaluation (for proposed mini-languages), and test criteria. Use after analysis, before planning. Bridges the gap between "what" and "how" so the planner can break the design into tasks.

From a design document, produces an implementation plan with ordered tasks, refactoring steps (P-steps before F-steps), domain assignments, and risks. Each task is one commit. Use after design, before implementation. Tasks reference specific files and are scoped tight enough to be independently committable.

Set up a TypeScript package to publish publicly on npmjs.com via the shared genvid-public-ci GitHub Actions recipe with OIDC trusted publishing (automatic provenance, no stored npm token). This is the rare, once-per-package setup nobody remembers the steps for, so reach for it WHENEVER someone wants a package onto npm or made publicly installable — even when they don't say "npm", "publish", or name the recipe. Trigger on requests like "open-sourcing this library", "make this package public", "get it onto npm so others can npm install it", "set up a release pipeline for this lib", "publish the first version to npmjs", "have releases show up on npm automatically", "wire up trusted publishing / provenance", "stop keeping an npm token in repo secrets", scoping a package under @genvid, or moving a repo from pnpm to npm or CircleCI to GitHub Actions for releasing. It owns the whole job — package.json publish-readiness, the ci.yml/publish.yml workflows, the lockfile migration, and the one-time npm bootstrap handoff — so prefer it over wiring these steps together ad hoc or a generic planning skill. Genvid-first, but the npm-readiness and OIDC steps apply to any package. Do NOT use it for a routine version bump or release tag of a package that already publishes, publishing to a private/internal registry (e.g. Azure Artifacts, GitHub Packages), adding or installing a dependency, or non-npm publishing such as Docker images, the Construct3 marketplace, or GitHub Pages.

Rebases a feature branch onto another branch (typically the project's default branch or another feature branch) with conflict resolution guidance and post-rebase verification. Use when the user asks to rebase, integrate upstream changes into a feature branch, squash before rebasing, or resolve merge conflicts during a rebase.

Rebases a feature branch onto the default branch after an earlier branch in its stack was squash-merged, skipping the now-obsolete merged commits via git rebase --onto. Use when the user mentions a stacked branch and reports that a parent was merged, or when a normal rebase produces unexpected conflicts that look like replayed already-merged work.

Cut a ROUTINE release of a package that ALREADY publishes to npmjs.com via the shared genvid-public-ci publish.yml OIDC recipe — bump, commit, tag, and trigger the publish workflow. The TAG push is what triggers publishing; there is no manual npm publish step. Reach for it whenever someone wants to ship a new version of an npm package that is already wired for OIDC publishing. Trigger on requests like "release the package", "cut a new version", "ship 0.2.0", "ship a patch", "bump and tag", "publish the new version to npm", or "push the release tag". It owns the whole job — state assessment and classification, version decision, the version bump commit, CHANGELOG move, tag creation, CI gate, and publish-run hand-off. Do NOT use it for: one-time publish setup where publish.yml is absent or not the v*.*.* OIDC recipe (use publish-npm-package instead; it owns that setup); releasing a marketplace plugin (use release-plugin); publishing to a private or internal registry (Azure Artifacts, GitHub Packages, etc.); or non-release work like adding a feature without shipping a version.

Cut a versioned release of a single Genvid marketplace plugin (a Claude Code plugin published through the genvid-holdings/claude-code-marketplace catalog), end to end across both repos: bump .claude-plugin/plugin.json, move the CHANGELOG Unreleased section, commit, push an annotated vX.Y.Z tag, and bump the plugin's marketplace source.ref. This is the rare, nobody-remembers-the- steps maintainer workflow, so reach for it WHENEVER someone wants a plugin release shipped — even when they don't name the steps. Trigger on requests like "release the plugin", "cut a new genvid-dev / genvid-c3 version", "bump the plugin version and ship it", "tag and publish the plugin", "push this to the marketplace", "make the new skill available to consumers", "publish the first version of this plugin", or "the tag / plugin.json version / marketplace ref are out of sync, fix the release". It owns the whole job — state assessment and reconciliation, the version + CHANGELOG bump, the annotated tag, the marketplace ref update, and the /plugin update handoff. Do NOT use it for: the consumer side of pulling a newer plugin into a repo (use sync-config); publishing an npm / TypeScript package to npmjs.com (use publish-npm-package); or routine non-release work like adding a skill without shipping a release.

1 hook across 1 event