Shared agent skills for Codervisor projects.
| Project | Repository | Skills |
|---|---|---|
| Ising | codervisor/ising |
codervisor-forge |
| Cueless | codervisor/cueless |
codervisor-forge |
| Synodic | codervisor/synodic |
codervisor-forge |
Agent-teachable knowledge bundles — each ships as SKILL.md + references + templates.
| Skill | Description | Audience |
|---|---|---|
git-commit |
Conventional commits, atomic staging, hook failure recovery | Any |
rust-node-bootstrap |
Scaffold a new Rust+Node.js hybrid project with all infrastructure | Rust+Node.js hybrid projects |
rust-npm-publish |
Publish Rust binaries to npm via the platform package pattern | Rust+Node.js hybrid projects |
rust-node-ci |
GitHub Actions CI/CD workflows and composite actions | Rust+Node.js hybrid projects |
See docs/catalog.md for the full catalog.
# Via skills CLI (recommended)
npx skills add codervisor/forge@<skill-name> -g -y
# Manual: copy skill directory to your project
cp -r skills/<skill-name> .github/skills/
# Git submodule (pinned version)
git submodule add https://github.com/codervisor/forge.git .forgeAfter installing a skill, copy any templates you need from skills/<skill-name>/templates/
into your project. GitHub Actions go into .github/actions/<name>/, workflows into .github/workflows/.
- Create
skills/<skill-name>/SKILL.mdfollowing the skill authoring guide - Add references, templates, and examples as needed
- Update docs/catalog.md with the new skill entry
- Open a PR — skills are validated for token budget (< 3000 tokens) and structure
Skills with templates use a config-driven approach. Each consuming repo provides
a config file (e.g., publish.config.ts) that declares project-specific values:
import type { PublishConfig } from '@codervisor/forge';
export default {
scope: '@myorg',
binaries: [
{ name: 'my-cli', scope: 'cli', cargoPackage: 'my-cli' },
],
platforms: ['darwin-x64', 'darwin-arm64', 'linux-x64', 'windows-x64'],
mainPackages: ['packages/cli'],
cargoWorkspace: 'Cargo.toml',
} satisfies PublishConfig;MIT