Skip to content

Commit 55b4f41

Browse files
committed
chore(skills): add repository development skill
1 parent a8b3476 commit 55b4f41

2 files changed

Lines changed: 34 additions & 0 deletions

File tree

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: torii-development
3+
description: Contributor workflow for dojoengine/torii. Use when implementing or reviewing changes in Torii indexer, processors, GraphQL/gRPC surfaces, SQLite migrations, and CI-aligned tests.
4+
---
5+
6+
# Torii Development
7+
8+
Use this skill to ship focused changes in `dojoengine/torii` with correct fixture handling and CI-like checks.
9+
10+
## Core Workflow
11+
12+
1. Identify impacted crates (`indexer`, `processors`, `sqlite`, `server`, `graphql`, `grpc`, `runner`, `cli`).
13+
2. Prepare fixtures:
14+
- `bash scripts/extract_test_db.sh`
15+
3. If Cairo artifacts changed, rebuild test assets:
16+
- `bash scripts/rebuild_test_artifacts.sh sozo katana`
17+
4. Build and test:
18+
- `cargo build --workspace`
19+
- `KATANA_RUNNER_BIN=katana cargo nextest run --all-features --workspace`
20+
- Use `bash scripts/selective_test.sh <base_branch>` for scoped runs
21+
5. Run formatting and lint checks:
22+
- `bash scripts/rust_fmt.sh --fix`
23+
- `bash scripts/clippy.sh`
24+
6. If migrations changed, run and verify migration steps for `crates/migrations`.
25+
26+
## PR Checklist
27+
28+
- Include migration impact explicitly when applicable.
29+
- Keep fixture updates in the same PR as related code changes.
30+
- Document validation commands and outcomes.
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
interface:
2+
display_name: "Torii Development"
3+
short_description: "Contributor workflow for dojoengine/torii"
4+
default_prompt: "Use $torii-development to implement and validate changes in torii."

0 commit comments

Comments
 (0)