Hi Anton, I am also not sure yet what the best way to contribute and share these skills is. A separate repository is only one option, so let’s discuss it.
A separate repository may be more convenient for user-facing skills: users could quickly clone or download them without getting the entire Ignite codebase. Sincerely, Dmitriy Pavlov ср, 2 сент. 2026 г. в 20:50, Anton Vinogradov <[email protected]>: > Good idea! But it's not clear how to share. > Could you please lead this? Please create the initial skills, publish them, > and provide instructions. > > For example, I used Clause and taught it to write AI-styled code. > > Btw, why a separate repository? > > On Wed, Sep 2, 2026 at 8:44 PM Dmitriy Pavlov <[email protected]> wrote: > > > Hi Igniters, > > > > Some of us have started creating AI-assisted automations and skills for > > Ignite 2. Some help contributors review changes, run tests, and > investigate > > failures, while others could help users work with the product. > > > > Instead of maintaining these tools individually, I suggest that we > combine > > our efforts and develop them openly as part of the Ignite ecosystem. This > > could become a new layer of open-source collaboration: sharing not only > > code and documentation, but also reusable development and operational > > workflows. > > > > Where should we maintain them? > > > > 1. In the main Ignite repository. > > 2. In a separate Ignite Skills repository. > > 3. Contributor skills in Ignite and user-facing skills separately. > > > > Which option would be most useful? What skills should we contribute > first? > > > > Sincerely, > > Dmitriy Pavlov > > > > P.S. As a first contribution, I would like to publish the > > documentation/release-note skill, which I believe is already working > quite > > well. > > >
