Frontmatter
| title | >- |
| author | nikeshadhikari9 |
| state | Merged |
| createdAt | Oct 1, 2025, 8:38 AM |
| updatedAt | Oct 8, 2025, 3:33 PM |
| closedAt | Oct 1, 2025, 9:59 AM |
| mergedAt | Oct 1, 2025, 9:59 AM |
| branches | dev ← docs/tab-container-maincontainer-jsdoc |
| url | https://github.com/neomjs/neo/pull/7314 |

Hello maintainers, could you please add hacktoberfest-accepted as label with the merged PR to make it valid for participation of hacktober fest.

Thanks, and welcome to the contributors log. How was the experience with the AI workflow?
One minor issue: looks like your IDE removed the block formatting. No worries, I can re-add it with just one keyboard shortcut. In case you want to work on more files, you are welcome to open your own tickets. Especially inside the examples folder, there should be plenty of files that need intent-driven documentation. Or ping me, and I can open more tickets.

Thanks a lot for the warm welcome! The AI-assisted was cool, I previously had use some AI Cli's but this gemini cli felt way easier and was really smooth setting up the knowledge base. And about the block formatting-I was using prettier on my IDE that performed auto formatting. I’ll make sure to be more careful next time, but glad it’s a quick fix on your end.
I’d definitely like to work on more files. The examples folder sounds like a great place to start. Please feel free to open more tickets or assign me if you think there are areas that need improvement.

Using eslint & prettier would indeed be an option (inside the repo itself). So far I only created an md file for coding guidelines, which gemini parses inside the agent file. So in theory, it should have known.
From a fun perspective, I would recommend .github/ISSUE/epic-enhance-workflow-with-mandatory-unit-testing.md. After the agents file instruction, point gemini to the local epic file, and then pick a sub to work on. The impressive part here is that gemini can (almost) completely resolve these migrations on its own. Sometimes you need to prompt versus derailments or give the hint that the neo related imports must be the same, but otherwise it combines the knowledge of siesta, playwright, neo and the small but mean differences when running neo inside node vs the browser on its own.
If you are up for it, please add a comment on one of the subs first, since i am working on the epic too (so that we don't collide). Of course every sub-ticket is worth its own PR.

hello @tobiu, I will continue from now. I was busy as it was nepalese most awaited festival Dashain.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch, not themainbranch