Hoi hoi! ๐
I'm @nyaomaru, a frontend engineer who loves TypeScript and cats! ๐ธ
Today, I have some exciting news!
I've created a new open-source organization called Necoz! ๐๐
Necoz ยท GitHub
A friendly open-source community building small, simple, and useful tools together. ๐ธ - Necoz
github.com
Why?
Well, my projects started as little tools I built for myself.
But over time, people started using them, reporting bugs, improving documentation, and contributing code.
YAY!!! ๐
And I realized something.
Open source is much more fun when we build things together!
So, I decided to give these projects a new home. ๐
๐ Small. Simple. Useful.
This is the philosophy behind Necoz.
We don't need to build something gigantic to make a difference.
A tiny utility can solve a real problem.
A small PR can make a project better.
Even fixing one typo can help someone!
That's what I love about open source. ๐ธ
๐ฑ Our Three Principles
๐ Open to Everyone
First-time contributor?
Experienced engineer?
Just found a typo?
EVERYONE IS WELCOME!!! ๐
You don't need to be an expert to contribute.
๐ ๏ธ Build Something Useful
Small tools. Simple solutions. Real problems.
A project doesn't need a thousand features to be valuable.
Sometimes one useful function is enough!
๐ธ Be a Good Cat
Be kind. Be curious. Respect others.
We can disagree about code, but we should always respect the people behind it.
And don't be afraid to make mistakes.
Even cats sometimes fall off tables! ๐น
๐ Our Projects
We're starting with two projects!
is-kit: A lightweight TypeScript toolkit for composing reusable type guards.
necoz-oss
/
is-kit
Build small guards. Compose them. A lightweight, zero-dependency toolkit for building reusable TypeScript type guards that compose, refine, and preserve natural narrowing. Runtime-safe ๐ก๏ธ, composable ๐งฉ, and ergonomic โจ.
is-kit
Build small guards. Compose them.
is-kit is a lightweight, zero-dependency toolkit for building reusable TypeScript type guards.
is-kit is not just a collection of isX helpers. Its main focus is composing
small runtime checks into reusable guards while preserving useful TypeScript
narrowing.
It helps you write small isFoo functions, compose them into richer runtime
checks, refine properties on values you already know about, and keep
TypeScript narrowing natural inside regular control flow. Use it at runtime
boundaries when needed, without requiring a schema-first workflow.
Runtime-safe ๐ก๏ธ, composable ๐งฉ, and ergonomic โจ without asking you to adopt a heavy schema workflow.
- Build and reuse typed guards
-
Compose guards with
and,or,not,oneOf - Use
refineKeyto narrow a child property while preserving its parent type - Validate object shapes and collections when that is useful
-
Parse or assert
unknownvalues without a large schema framework
Bestโฆ
changelog-bot: A tool that helps generate useful changelogs from GitHub project history.
necoz-oss
/
changelog-bot
Automatic create changelog with AI. ๐ค It provides CLI and github actions. ๐ https://www.npmjs.com/package/@nyaomaru/changelog-bot
Releases should feel exciting, not tedious.
@nyaomaru/changelog-bot ๐ค turns your Git history and release notes into a polished changelog entry (and optional PR) in a single run. Drop it into CI, run it locally, or hand it to your release captainโeither way, you ship with a crisp changelog and zero copy-paste fatigue.
The GitHub repository is necoz-oss/changelog-bot. The npm package name is still @nyaomaru/changelog-bot. In workflows, use necoz-oss/changelog-bot. GitHub Actions does not follow repository redirects for actions or reusable workflows, so keep uses: on the new owner. Web and git URLs for nyaomaru/changelog-bot still redirect.
Why changelog-bot?
- Automated storytelling: Combines commit history, PR titles, and release notes to produce human-ready changelog sections.
- LLM superpowers (optional): Connect OpenAI or Anthropic for tone-aware summaries or skip API keys entirely and rely on a robust heuristic fallback.
- PR-ready output: Can open a pull request with updated changelog, compare links, andโฆ
Both started as personal projects.
Now, they're part of Necoz!
And hopefully, more little projects will join us someday. ๐ธ
๐ Welcome to Necoz, John!
And guess what?
@johnnylemonny has already joined Necoz! ๐๐
YAY!!! Our little cat family is growing! ๐ธ
I'm really happy to have him on board!
Welcome, John! Let's build something awesome together! ๐
โค๏ธ Let's Build Together!
To everyone who has contributed to my projects so far...
THANK YOU!!! ๐
Every Issue, PR, suggestion, and Star means a lot.
I don't know how big Necoz will become.
And that's okay!
What matters is building useful things, learning together, and making open source a welcoming place.
One small contribution at a time.
- ๐ GitHub: https://github.com/necoz-oss
- ๐ Website: https://necoz.co/
If something catches your interest, feel free to join us!
And if you like our projects, a โญ would make these little cats very happy! ๐ธ
Stay a Good Cat! ๐ธ
Thank you for reading! ๐คฒ
Top comments (67)
Hey nyaomaru! ๐ธ Congratulations on launching Necoz!
I love the philosophy of building small, simple, and useful tools together. As a developer and open-source creator, Iโm excited to see a community that values collaboration, learning, and welcoming contributors of all experience levels.
Iโd love to join Necoz, contribute to your projects, and learn alongside the community. Looking forward to building something useful together! ๐
Welcome to the Necoz community, Prasoon! It's fantastic to have fellow open-source builders join in. Feel free to explore the projects under necoz-oss - both
changelog-botandis-kitare great places to start, and we'd love to see your contributions and feedback. Looking forward to building cool tools together! ๐ธ๐Thank you so much, John! ๐ธ๐ I'm excited to be part of the Necoz community. I'll explore
changelog-botandis-kitand look for ways to contribute. Looking forward to learning, sharing feedback, and building useful open-source tools together. Happy to be here!Thank you so much, Prasoon! ๐ธ๐
Iโm really happy to hear that!
Youโre absolutely welcome to join Necoz and contribute to any project that interests you. Issues, docs, tests, code, ideas, anything is welcome. ๐
Looking forward to building and learning together! ๐
Thank you so much for the warm welcome! ๐ธ๐
Iโm really excited to join Necoz and contribute to the projects. Iโll explore the repositories and look for an issue where I can make my first contribution.
Looking forward to learning, building, and growing together with the community! ๐
Huge congrats on officially launching Necoz, @nyaomaru! Collaborating with you on
changelog-bothas been a great experience, and the "Small. Simple. Useful." philosophy really shows in how welcoming and practical the projects are. I'm really glad to be part of thenecoz-ossorganization and excited to keep building useful tools together with this community. ๐ธ๐Thank you so much, John! ๐ธ๐
Iโm really happy to have you as part of Necoz.
Working together on changelog-bot has already been such a great experience, and Iโm excited to keep building more useful things together! ๐๐
Letโs keep going! ๐ธ
Hey @nyaomaru, maybe create the Necoz organization here too! I'd love to contribute on DEV.to as a member as well! We would join forces, and I think this would help the Necoz projects on GitHub.
Thatโs actually a really nice idea! ๐ธ๐
Iโd definitely like to look into it! ๐โจ
And Iโd be really happy to have you contribute there as well.
Thanks! Joined!
100%! Looking forward to everything we'll ship next with Necoz. Letโs make it awesome! ๐ธ๐
Bravo that is really cool way to think, may be try latter to commit and have commits and feedacks on your repo!
Thank you so much! ๐ธ๐
Yes, please feel free to check out the repo anytime!
Feedback, issues, and contributions are always welcome. ๐โจ
I have a single-file Pyodide laboratory for reproducible numerical experiments, MIT-licensed, zero dependencies, one HTML file. It fits your Small/Simple/Useful philosophy โ would you be open to it joining Necoz as a project? github.com/19algorythms/probat (just made a post about it).
Thanks for sharing it! ๐ธ
I took a look, and the idea definitely fits the Small. Simple. Useful. philosophy.
For now, though, Iโd like Necoz to stay centered around projects maintained by people who are actively involved in the community.
So Iโd be open to revisiting this if youโd like to contribute to Necoz and continue actively maintaining probat as part of it. ๐
I donโt want Necoz to become just a collection of transferred repositories. Iโd like each project to have someone who genuinely cares for it and keeps building it with the community.
Ok, sorry I proposed it by the time I got your answer. Anyway your project is very cool! My idea was to try to be involved in a community and it is as you want. Have a bright day or night :D
We would love to have you on board, @19algorythms! If you are looking for a place to jump in, there are currently two open
good first issuetasks waiting in changelog-bot issues - adding a Jest coverage command (#297) and extracting reusable test fixtures (#296). Feel free to grab whichever one looks fun to you and leave a comment on the issue. ๐ธ๐No need to apologize at all! ๐ธ
I was genuinely really happy that you thought of Necoz and wanted to bring your project into the community.
If youโd still like to get involved, please feel free to join us and contribute anytime! ๐๐
And thank you so much for the kind words too. Hope you have a bright day or night as well! ๐ธ
Thank you! I took on #297. PR here: github.com/necoz-oss/changelog-bot.... Great first step into open source culture! :D
Thx! ๐ธ๐
Thatโs a great contribution and a really nice first step into open source! ๐
I left you one tiny bit of homework on the PR too. ๐น
If you have some time, try narrowing the coverage target with
collectCoverageFrom.No rush at all, though! ๐
Thank you for taking care of it! ๐ธ๐
I merged the PR. ๐
Really appreciate the contribution, and I hope we can work together again! ๐
Congratulations ๐ ๐Wow, this is such a beautiful thing, it's really great! @johnnylemonny did a wonderful job. I would be happy to contribute to it, but I need 3 months. I'll be ready to contribute after launching my game. Awesome, cool! And yes, the cover image deserves praise too, always OP๐ฅ
Thank you so much! ๐ธ๐ฅ
Thereโs no rush at all. Necoz is open to everyone anytime, so if you ever feel like contributing, just jump in whenever it feels right! ๐๐
And your game sounds exciting too! ๐ฎ
Iโm looking forward to seeing it when you launch it!
Also, thank you for the cover image compliment! ๐น๐จ
Best Dev.to cover image award 2026 goes to mr. @nyaomaru โ ๏ธ๐
Yeah๐๐ป
Thank you so much for the kind words! Best of luck with your game launch - that sounds super exciting. Take all the time you need, and we'd be thrilled to welcome you whenever you are ready to jump in. Really glad you liked the cover art too! ๐ฎ๐
Congrats on launching Necoz! The "small, simple, useful" philosophy really resonates โ I like that is-kit focuses on composing small type guards into reusable checks instead of asking people to adopt a heavy schema workflow, and that changelog-bot turns real Git history and release notes into something readable. The part that stood out most was welcoming first-time contributors, including typo fixes; that low bar for a first contribution is exactly what turns readers into maintainers. Wishing the little cat family well!
Thank you so much! That path from fixing a single typo to becoming an active maintainer is exactly what open source should feel like. Keeping tools like
changelog-botlightweight and focused makes jumping into the code way less intimidating, especially for first-time contributors. We really appreciate the kind words and the warm wishes for the cat family! ๐ธ๐Thank you so much! ๐ธ๐
And I really love โthe little cat family.โ ๐น
Thatโs exactly the kind of community I hope Necoz can become: a place where someone can start with a tiny contribution and gradually become more involved.
Iโm really looking forward to growing it together with everyone! ๐โจ
I really like the idea behind Necoz, especially the focus on keeping projects small, simple, and useful. Open-source communities become more welcoming when beginners can contribute through documentation, testing, or even small fixes instead of feeling they need to be experienced developers first. Looking forward to seeing how the community and its projects grow!
Thank you so much! Keeping the barrier to entry low is definitely the main goal. Documentation improvements, small test fixes, and minor refactors are just as impactful as big features. We are really excited to see the community grow around that idea and to welcome more developers along the way! ๐ธ๐
Absolutely! Making beginners feel welcome is a great way to build a stronger open-source community. Small contributions can be the first step toward bigger projects. Looking forward to seeing Necoz grow!
Thank you! ๐ธ๐
Thatโs exactly what I hope to see with Necoz too.
A tiny first contribution can lead to the next one, and before you know it, someone who was nervous about contributing is confidently helping shape the project. ๐โจ
Iโm really looking forward to growing this community together! ๐ธ
This is so cool, we need more initiatives like that! If I had a second life, I'd definitely contribute ๐ฅฐ๐ป
Aww, thank you so much! ๐ธ
And haha, I totally get that feeling. ๐น
Even cheering us on like this already means a lot!
If that second life ever appears, Necoz will be waiting for you. ๐โจ
Congratulations on giving these a proper home โ the "small, simple, useful" line is exactly what I look for in tools I can actually keep using in small-business work. A big framework is easy to start and hard to maintain; a small guard or a changelog helper that does one job well is much easier to trust, and much easier to hand over to someone else.
What stood out to me was the welcome for first-time contributors, including typo fixes. That's usually how people learn a codebase without the pressure of a huge feature โ and it's how a lot of useful small tools stay alive. The is-kit idea especially clicked for me: composing small runtime checks into reusable guards, without dragging in a heavy schema setup, sounds like the kind of thing that quietly prevents the messy data bugs that cost real time later.
Thank you so much for such a thoughtful comment! ๐ธ๐
What you described is very close to what I want Necoz to be.
I really like tools that do one thing well, stay small enough to understand, and are easy to trust and maintain over time. That was a big part of the motivation behind both
is-kitandchangelog-bot.Iโm especially happy that the
is-kitidea clicked with you. ๐ธThat โsmall runtime checks composed into reusable guardsโ philosophy is exactly what I want to keep simple and practical.
Thanks again for taking the time to read it so carefully! ๐โจ
Thats a great ideaโบ๏ธ
beluga's profile picture bro
Yeah im a fan of begula๐
Haha, I noticed the Beluga profile picture too! ๐น๐
Thank you! Welcome to Necoz! ๐ธ๐
Clean architecture is easy to maintain in a slide deck; the real test is how gracefully the system degrades under cascading production failures.
Minimizing abstraction layers and owning your critical runtime path will always outperform adding more third-party glue.
Absolutely. ๐ธ
A clean diagram is nice, but production failures are where the architecture really proves itself.
I also tend to prefer fewer layers and a smaller critical runtime path. The less hidden glue there is, the easier it is to understand what actually failed and recover gracefully. ๐
Some comments may only be visible to logged-in visitors. Sign in to view all comments.