Hi Dmitriy, Anton and all, I fully support the initiative to create and publish AI‑assisted skills for Ignite.
After thinking about the options, I prefer Option 3 – contributor skills in the main Ignite repo, and user‑facing skills in a separate repository. Here’s why: For contributor skills (inside the main repo): - Version coherence – they evolve with the codebase, so we never have mismatched versions between a skill and the actual source tree. - Simpler PR workflow – contributors use the same repo, same CI, same issue tracker – no extra overhead. - Single source of truth – developers know exactly where to find and update helper scripts. For user‑facing skills (separate repo): - Low‑friction for end users – they can clone or download just the skills without pulling the entire Ignite codebase (which is large). - Cleaner focus – users don’t have to navigate through project internals; they get a dedicated space with clear documentation tailored to their use cases. - Independent versioning – we can release updates to user skills more frequently, without waiting for an Ignite release. Best regards, Dmitry Werner On Wed, Sep 2, 2026 at 10:53 PM Dmitriy Pavlov <[email protected]> wrote: > 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. > > > > > >
