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! 🐈🎉
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 (18)
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! 😸
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. 😸🚀Bro thats fire 🔥
Fire! 😸🔥
Cool❤️🥰
I’m planning to add a new stage to this website too!
Stay tuned! 😸🎮
This is so cool, we need more initiatives like that! If I had a second life, I'd definitely contribute 🥰😻
Thats a great idea☺️
beluga's profile picture bro
Yeah im a fan of begula😅
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.