Skip to content
This repository was archived by the owner on May 19, 2026. It is now read-only.

Latest commit

 

History

History
56 lines (44 loc) · 2.56 KB

File metadata and controls

56 lines (44 loc) · 2.56 KB

Migrated

This repository's skills bundle has moved to onsager-ai/dev-skills as part of a cross-repo consolidation of engineering-methodology skills shared across onsager-ai/* and codervisor/* projects. This repo is now archived.

Where each skill lives now

Skill New home
git-commit onsager-ai/dev-skills/skills/git-commit
github-integration onsager-ai/dev-skills/skills/github-integration
parallel-worktrees onsager-ai/dev-skills/skills/parallel-worktrees
rust-node-bootstrap onsager-ai/dev-skills/skills/rust-node-bootstrap
rust-node-ci onsager-ai/dev-skills/skills/rust-node-ci
rust-npm-publish onsager-ai/dev-skills/skills/rust-npm-publish

Install all of them globally:

npx skills add -g onsager-ai/dev-skills --skill '*' -a claude-code

Or a single skill:

npx skills add -g onsager-ai/dev-skills --skill rust-node-ci -a claude-code

Each skill's git history was preserved during migration (via git subtree split for skills with substantial history; copies with Import … commit messages for smaller skills referencing the source SHA).

What about the GitHub Actions in actions/?

The composite actions under actions/ (setup-workspace, rust-cross-build, compute-version, wait-npm-propagation) were not part of the skills migration. Consumers that referenced them by ref (e.g. uses: codervisor/forge/actions/setup-workspace@main) should keep working against this archived repo — GitHub's archive state preserves all refs. If you need to evolve any of those actions, fork them into your own repo.

Why the move

The skills here had drifted across onsager-ai/onsager, onsager-ai/onsager-skills, onsager-ai/duhem, and codervisor/lean-spec — each carrying its own copy or vendoring forge via npx skills add. Consolidating into a single onsager-ai/dev-skills bundle (one global install per machine, single PR loop to evolve a skill) is simpler than maintaining parallel copies and per-repo skills-lock.json entries pointing at this repo.