skill for stellar wizard update

[ozgunozerk]

Opening the same one with: OpenZeppelin/openzeppelin-skills#5

@brozorec I'm pushing the base for the skill. Please feel free to update/change/improve it after your trials.

We think this can be generalized for other projects we have. For that, let's have more discussion with other teams, collect input, and then if everyone thinks that makes sense, we can also craft a generalized template for that in the repo.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 3806670c-c27d-465f-bdd6-d6ce03ecaa35

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch stellar-wizard-skill

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ozgunozerk]

I think step 3 is very stellar specific, and does not add much value for the LLM's considering they are very capable. I'm getting more inclined to remove step 3 altogether

[ericglau]

This looks great! Left some minor feedback.

Do you think it would also be useful to have a separate skill (outside the scope of this skill/PR) that instructs how to update the various other packages and contents to match, aside from the main UI and core packages? Or do you find the agent already knows how to do those, such as by looking at CONTRIBUTING.md? For example, AI descriptions in common, ui/api/ai-assistant/function-definitions, mcp, changeset additions, creation/regeneration of test snapshots using ava, etc.

[ozgunozerk]

This looks great! Left some minor feedback.

Thanks a lot!

Do you think it would also be useful to have a separate skill (outside the scope of this skill/PR) that instructs how to update the various other packages and contents to match, aside from the main UI and core packages? Or do you find the agent already knows how to do those, such as by looking at CONTRIBUTING.md? For example, AI descriptions in common, ui/api/ai-assistant/function-definitions, mcp, changeset additions, creation/regeneration of test snapshots using ava, etc.

I honestly don't have much idea on what else is going on in wizard aside from the main UI and core packages, so I don't have a good opinion on this one, sorry :)

[brozorec]

Does it make sense to organize it like this to add ecosystem-specific instructions and mappings to each reference whereSKILL.md contains the generic flow and an index.