Claude-skill-registry end-to-end-tests

after making changes, run end-to-end tests to ensure that the product still works

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/end-to-end-tests" ~/.claude/skills/majiayu000-claude-skill-registry-end-to-end-tests && rm -rf "$T"

manifest: skills/data/end-to-end-tests/SKILL.md

source content

End-to-end tests

Instructions

When you are done making changes, run all end-to-end tests through this command:

make cuke

If the exit code is 1, read the error messages and fix all errors, then re-run the end-to-end tests until they run successfully and exit with code 0.

End-to-end tests are defined in the "features" folder. They are written in the Gherkin language and execute using Cucumber for Go.

If an end-to-end test fails, you can re-run only this test to verify that your fix works:

Add the
```
@debug @this
```
tag to a specific scenario
Run
```
make cukethis
```
to execute only the tagged scenario
when the test passes, remove the
```
@debug @this
```
tags