Agent skill

Rocky Dev

Top-level router for Rocky development tasks. An agent skill from rocky-data/rocky.

Apache-2.0Auto-check passedDevelopment

Install Rocky Dev

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rocky-dev .claude/skills/rocky-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .claude/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/rocky-dev .agents/skills/rocky-dev && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .agents/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/rocky-dev .cursor/skills/rocky-dev && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .cursor/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rocky-data/rocky.git --path .agents/skills/rocky-dev

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/rocky-dev .gemini/skills/rocky-dev && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .gemini/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/rocky-dev .github/skills/rocky-dev && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .github/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rocky-data/rocky --skill rocky-dev -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rocky-dev --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/rocky-dev .opencode/skills/rocky-dev && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rocky-dev" agent skill from https://github.com/rocky-data/rocky/tree/main/.agents/skills/rocky-dev into .opencode/skills/rocky-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocky-dev", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: rocky-dev
GitHub stars: 304
Token cost: ~2.1k tokens
SKILL.md length: 842 words
Files: 1
Skills in repo: 22
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Top-level router for Rocky development tasks. An agent skill from rocky-data/rocky.

Quick monorepo orientation (build
SKILL.md covers The subprojects at a glance, Monorepo commands (from root), Route by task and Cross-cascade reference table, plus 4 more sections
Calls just, uv and cargo
Tasks that involve Monorepo tooling

What it does

Rocky Dev is an agent skill from rocky-data/rocky. Top-level router for Rocky development tasks. Use this FIRST for any request to change Rocky — it points at the right subskill based on what's being touched. Also use for quick monorepo orientation (build, test, lint, install, where-is-what).

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Monorepo tooling and Data warehousing. It works with Dagster, Visual Studio Code, npm and Python. The repository describes itself as: A SQL transformation engine that type-checks your whole pipeline and catches breaking changes before they run — branches, replay, column-level lineage, compile-time contracts… The licence is Apache-2.0.

When your agent uses it

Quick monorepo orientation (build
Tasks that involve Monorepo tooling
Tasks that involve Data warehousing

Example prompts

“/rocky-dev”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 0cb7c7b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- just
- uv
- cargo
- npm
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rocky Dev loads about 2.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 842 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rocky-data/rocky at commit 0cb7c7b, republished under its Apache-2.0 licence (© rocky-data). 842 words, ~2,142 tokens.

Download SKILL.mdSave it as .claude/skills/rocky-dev/SKILL.md (or your agent's skills folder).

name: rocky-dev
description: Top-level router for Rocky development tasks. Use this FIRST for any request to change Rocky — it points at the right subskill based on what's being touched. Also use for quick monorepo orientation (build, test, lint, install, where-is-what).

Rocky dev router

Rocky is a monorepo with four shipping subprojects + a playground catalog. Most non-trivial changes cross subproject boundaries, and the cascade rules are easy to forget. Use this skill as a router.

The subprojects at a glance

Path	Language	Ships as	Build	Test
`engine/`	Rust	`rocky` + `rocky-lsp` binaries	`cargo build --release`	`cargo test`
`sdk/python/`	Python	`rocky-sdk` wheel	`uv build`	`uv run pytest`
`integrations/dagster/`	Python	`dagster-rocky` wheel	`uv build --wheel`	`uv run pytest`
`editors/vscode/`	TypeScript	Rocky VSIX	`npm run compile`	`npm run test:unit`
`examples/playground/`	Config	(not published)	`./run.sh` per POC	`./scripts/run-all-duckdb.sh`

Each has its own AGENTS.md with subproject-specific coding standards and commands. Read the subproject AGENTS.md before editing it — they're kept current.

Monorepo commands (from root)

bash

just build       # cargo build --release + uv build --wheel + npm compile
just test        # cargo test + pytest + vitest (vscode unit tests only)
just lint        # cargo clippy/fmt + ruff + eslint
just codegen     # Rust → JSON schemas → Pydantic + TypeScript
just --list      # all recipes

Each subproject's native tool (cargo, uv, npm) also works directly from inside the subproject dir. The justfile is convenience, not a requirement.

Route by task

"Change the CLI's JSON output" (add field, new command, rename)

→ rocky-codegen skill. You'll edit Rust in engine/crates/rocky-cli/src/output.rs then run just codegen. The CI drift check will fail the PR if you skip this.

"Add a new `rocky <command>` subcommand"

→ rocky-new-cli-command skill. This is the superset that walks through engine impl + codegen + dagster resource method + vscode command registration.

"Change Rocky DSL syntax (`.rocky` files)"

→ rocky-dsl-change skill. Lockstep change across engine/crates/rocky-lang, engine/crates/rocky-compiler, editors/vscode/syntaxes/rocky.tmLanguage.json, editors/vscode/snippets/rocky.json, docs/src/content/docs/concepts/rocky-dsl.md, and docs/rocky-lang-spec.md.

"Add a new warehouse or source adapter"

→ rocky-new-adapter skill. New crate under engine/crates/rocky-<name>/, implementing traits from rocky-adapter-sdk, with conformance tests. Template crates: rocky-databricks, rocky-snowflake, rocky-duckdb, rocky-fivetran.

"Demo a feature with a POC"

→ rocky-poc skill. Scaffold with examples/playground/scripts/new-poc.sh <category> <id-name>. Defaults to DuckDB; credential-gated POCs must fail fast. Do NOT duplicate anything from engine/examples/ (official starter set).

"Write or review a `rocky.toml`"

→ rocky-config skill. Covers the 4 pipeline types (replication / transformation / quality / snapshot), adapter variants (duckdb / databricks / snowflake / fivetran), minimal-config defaults, env-var substitution (${VAR:-default}), governance, checks, contracts, state backends, hooks. Also lists the legacy keys that no longer work ([source], [warehouse], [replication], [checks] at top level).

"Cut a release"

→ rocky-release skill. Tag-namespaced (engine-v*, sdk-v*, dagster-v*, vscode-v*). All four artifacts are CI-driven — land a release PR with the version bump + CHANGELOG entry, tag the merged commit, push the tag, and the matching release workflow handles the build and publish. Release rocky-sdk before any dagster-rocky release that raises its rocky-sdk>= floor. scripts/release.sh remains as a local-build hotfix fallback. Convenience recipes: just release-engine, just release-sdk, just release-dagster, just release-vscode.

"Change Databricks / Snowflake / Fivetran integration behavior"

→ Use the engine-local databricks, fivetran, or rocky skill when the active agent client exposes it. If it is not available, start with engine/AGENTS.md and the referenced adapter source and API documentation.

"Something Dagster-specific"

→ Also use an up-to-date Dagster specialist skill when one is available in the active agent client. The integration at integrations/dagster/ leans on Dagster's current component/pipes/asset model, which evolves quickly.

Show full SKILL.md (382 more words)Show less

Cross-cascade reference table

When a change touches X, what else moves?

You change	Also touch
`engine/crates/rocky-cli/src/output.rs` (any `*Output` struct)	Run `just codegen` — auto-regenerates `schemas/`, `sdk/python/src/rocky_sdk/types_generated/`, `editors/vscode/src/types/generated/`. Then in `sdk/python/src/rocky_sdk/types.py`: re-export the new type and add a `parse_rocky_output()` dispatch entry (the hand-written runtime models there are gated by `test_schema_parity.py`, not codegen); `dagster_rocky.types` re-exports from `rocky_sdk`.
A `.rocky` keyword or operator	`engine/crates/rocky-lang/src/{token,parser,lower}.rs`, `engine/crates/rocky-compiler/src/`, `editors/vscode/syntaxes/rocky.tmLanguage.json`, `editors/vscode/snippets/rocky.json`, `docs/src/content/docs/concepts/rocky-dsl.md`, `docs/rocky-lang-spec.md`
A new CLI command	Engine impl + `rocky-cli/src/output.rs` struct + `rocky-cli/src/commands/export_schemas.rs` registration + `just codegen` + dagster `resource.py` method + vscode `src/commands/<group>.ts` + `package.json` contribution
A new adapter	New crate in `engine/crates/` + `engine/Cargo.toml` members + conformance test hookup + factory registration in `rocky-core/src/config.rs`
`rocky.toml` config schema	`engine/crates/rocky-core/src/config.rs` + `editors/vscode/schemas/rocky-config.schema.json` (for IDE autocompletion)
Test fixture for dagster	`just regen-fixtures` (writes to `integrations/dagster/tests/fixtures_generated/` for drift detection) or `./scripts/regen_fixtures.sh --in-place` to promote to `fixtures/` (destructive)

Optional: install local hooks

bash

just install-hooks

This sets core.hooksPath to .git-hooks/. The pre-commit hook runs just codegen and fails the commit if engine/crates/rocky-cli/src/output.rs, commands/doctor.rs, or commands/export_schemas.rs is staged and the regenerated bindings differ from what's staged — same invariant as the CI drift check, caught locally. Skip with ROCKY_SKIP_CODEGEN_HOOK=1 git commit … in emergencies.

Key invariants

Never commit a Rust *Output change without the regenerated bindings — codegen-drift.yml will fail the PR.
Never include Co-Authored-By trailers in commit messages. Use conventional commits (feat:, fix:, refactor:, test:, docs:, chore:), scoped by crate or subproject.
Never format!() untrusted input into SQL — use rocky-sql/validation.rs to validate identifiers first.
Never hand-edit files under */types_generated/ or */types/generated/ except the curated __init__.py / index.ts barrels (those are protected by git checkout in the codegen recipes).
Never skip hooks (--no-verify). The dagster integration has git hooks under integrations/dagster/.git-hooks/ for ruff + conventional commit validation + pytest.

Release cadence

Four artifacts, four tag namespaces, independent release schedules:

engine-v* → GitHub Releases (all 5 platform targets built in CI by engine-release.yml)
sdk-v* → PyPI (rocky-sdk) — ships before any dagster release that raises its floor
dagster-v* → GitHub Releases + PyPI
vscode-v* → GitHub Releases + VS Code Marketplace

See the rocky-release skill for the full checklist.

Reference files worth remembering

AGENTS.md (root) — monorepo-wide cascade rules
engine/AGENTS.md — engine coding standards, JSON output schema table, Databricks SQL patterns, auth flows
integrations/dagster/AGENTS.md — dagster layer architecture, "Adding support for a new Rocky CLI command" 9-step checklist
editors/vscode/AGENTS.md — vscode extension architecture + command table
examples/playground/AGENTS.md — POC authoring conventions
justfile (root) — orchestration recipes (build, test, lint, codegen, release, fixtures)
.github/workflows/ — path-filtered CI per subproject

Files

Just SKILL.md in .agents/skills/rocky-dev of rocky-data/rocky.

Open the folder on GitHubat commit 0cb7c7b

Compare with similar skills

Rocky Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rocky Dev compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rocky Dev this skillrocky-data/rocky	304	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Claude Settings Auditgetsentry/skills	1k	4 repos	~3k	Automated safety check: Pass	Apache-2.0	5 days ago
Blockless Extension E2EFreakStudioCN/mpy-hardware-extension	118	—	~1.2k	Automated safety check: Notes	Custom licence	9 days ago
Run E2E Testsmicrosoft/vscode-python-environments	141	—	~1.2k	Automated safety check: Pass	MIT	today
Databuddy Internaldatabuddy-analytics/Databuddy	1.2k	—	~11k	Automated safety check: Notes	AGPL-3.0	today
Nx Run Tasksnomcopter/react-mosaic	4.8k	7 repos	~613	Automated safety check: Pass	Custom licence	9 days ago

Similar skills

Claude Settings Audit
getsentry/skills
Official
Analyze a repository to generate recommended Claude Code settings.json permissions.
1k GitHub starsUsed in 4 repos~3k tokens
DevelopmentAuto-check passed
Blockless Extension E2E
FreakStudioCN/mpy-hardware-extension
Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…
118 GitHub stars~1.2k tokensUpdated 9 days ago
Testing & QAAuto-check: notes
Run E2E Tests
microsoft/vscode-python-environments
Official
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection.
141 GitHub stars~1.2k tokensUpdated today
Testing & QAAuto-check passed
Databuddy Internal
databuddy-analytics/Databuddy
Work inside the Databuddy monorepo for internal implementation, debugging, review, and refactoring.
1.2k GitHub stars~11k tokensUpdated today
DevelopmentAuto-check: notes
Nx Run Tasks
nomcopter/react-mosaic
Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.
4.8k GitHub starsUsed in 7 repos~613 tokens
DevelopmentAuto-check passed
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
55k GitHub stars~3.8k tokensUpdated today
DevelopmentAuto-check passed

Questions about Rocky Dev

What does Rocky Dev do?

Top-level router for Rocky development tasks. An agent skill from rocky-data/rocky. Rocky Dev is an agent skill from rocky-data/rocky. Top-level router for Rocky development tasks.

When should I use Rocky Dev?

Rocky Dev fits situations like: quick monorepo orientation (build; tasks that involve Monorepo tooling; tasks that involve Data warehousing.

How do I install Rocky Dev in Claude Code?

Run `npx skills add rocky-data/rocky --skill rocky-dev -a claude-code`. Or copy the skill folder (.agents/skills/rocky-dev in rocky-data/rocky) into .claude/skills/rocky-dev in your project. Claude Code loads it when a task matches its description.

How do I install Rocky Dev in Codex?

Run `npx skills add rocky-data/rocky --skill rocky-dev -a codex`. Or copy the skill folder (.agents/skills/rocky-dev in rocky-data/rocky) into .agents/skills/rocky-dev in your project. Codex loads it when a task matches its description.

Can I use Rocky Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rocky-data/rocky --skill rocky-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rocky-dev, .gemini/skills/rocky-dev, .github/skills/rocky-dev and .opencode/skills/rocky-dev in your project.

What does Rocky Dev need to run?

Going by SKILL.md and its folder, Rocky Dev needs the command-line tools its instructions call (just, uv, cargo, npm and git). Our summary lists: Python 3.

Does Rocky Dev access the network?

SKILL.md contains no URLs. Its commands use uv, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Rocky Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rocky Dev use?

Rocky Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rocky Dev use?

About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rocky Dev?

Skills that share tags, products or a category with Rocky Dev: Claude Settings Audit (getsentry/skills, 1k stars), Blockless Extension E2E (FreakStudioCN/mpy-hardware-extension, 118 stars), Run E2E Tests (microsoft/vscode-python-environments, 141 stars) and Databuddy Internal (databuddy-analytics/Databuddy, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rocky Dev?

rocky-data (a GitHub organization) maintains it in rocky-data/rocky, which has 304 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 7, 2026.

Source: rocky-data/rocky on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Rocky Dev

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Rocky dev router

The subprojects at a glance

Monorepo commands (from root)

Route by task

"Change the CLI's JSON output" (add field, new command, rename)

"Add a new rocky <command> subcommand"

"Change Rocky DSL syntax (.rocky files)"

"Add a new warehouse or source adapter"

"Demo a feature with a POC"

"Write or review a rocky.toml"

"Cut a release"

"Change Databricks / Snowflake / Fivetran integration behavior"

"Something Dagster-specific"

Cross-cascade reference table

Optional: install local hooks

Key invariants

Release cadence

Reference files worth remembering

Files

Compare with similar skills

Similar skills

More from rocky-data/rocky

Related

Questions about Rocky Dev

"Add a new `rocky <command>` subcommand"

"Change Rocky DSL syntax (`.rocky` files)"

"Write or review a `rocky.toml`"