Skip to content

Add cardonnay-sync skill - #3556

Open
OlufemiAdeOlusile wants to merge 2 commits into
masterfrom
add-cardonnay-sync-skill
Open

Add cardonnay-sync skill#3556
OlufemiAdeOlusile wants to merge 2 commits into
masterfrom
add-cardonnay-sync-skill

Conversation

@OlufemiAdeOlusile

Copy link
Copy Markdown
Collaborator

Summary

  • Adds the cardonnay-sync skill to this repo so it is available to anyone who clones cardano-node-tests, instead of staying local to one developer's Claude Code setup.
  • The skill documents how to point this repo's cardonnay dependency at an unreleased branch or commit for a real test run, so results are not silently produced against a stale PyPI release.

Test plan

  • Confirm the skill is picked up by Claude Code when opened in this repo

@OlufemiAdeOlusile
OlufemiAdeOlusile force-pushed the add-cardonnay-sync-skill branch 3 times, most recently from 868a959 to bbd9b6a Compare July 28, 2026 10:33
Add a skill documenting how to point this repo's cardonnay
dependency at an unreleased branch or commit so a test run actually
exercises that change instead of a stale PyPI release.
@OlufemiAdeOlusile
OlufemiAdeOlusile force-pushed the add-cardonnay-sync-skill branch from bbd9b6a to 0754533 Compare July 28, 2026 10:37

```sh
nix develop --accept-flake-config . -c bash -c "make update-uv-lock"
```

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Running uv lock is enough.

Comment thread .claude/skills/cardonnay-sync/SKILL.md Outdated

```sh
rm -rf run_workdir/.venv
```

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The step 5. is not needed. The whole content of run_workdir is wiped during testrun setup anyway.

Comment thread .claude/skills/cardonnay-sync/SKILL.md Outdated

6. Now run the actual test (`runner/node_upgrade.sh`, or a plain
`make cluster-scripts && make start-cluster` for a quicker smoke check).
This is the first point where it's actually exercising the real change.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make cluster-scripts && make start-cluster is only relevant for local development and will use the existing ./.venv, so this is incorrect. The change applies only to situations when the whole env is recreated, i.e. when using runner/regression.sh, runner/node_upgrade.sh, make test-env or make install.

Simplify lock regeneration to plain `uv lock`, drop the unnecessary
run_workdir/.venv cleanup step, and correct which commands actually
rebuild the environment (make cluster-scripts/start-cluster reuse the
existing .venv and don't exercise a synced ref).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants