DEV Community: Alizay Yousfzai

StackSpirit: a local ghost that tells you what to install

Alizay Yousfzai — Fri, 30 Oct 2026 18:15:46 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge: Week 4.

What I Built

I kept watching the same failure. Someone wants to build a Next.js site, or a Python script that clicks through a browser, or an agent with Google's ADK, and they never get to the interesting part. The README says npm install and assumes Node 20. Their machine has Node 16, or Python without venv, or no GOOGLE_API_KEY. The error is real, and it is also useless if you are new.

I wrote StackSpirit for that moment. It is a small open-source CLI. You tell it what you want to build:

stackspirit check "Next.js website"
stackspirit check "AI agent with Google ADK"
stackspirit check "Python automation with Playwright"
stackspirit check "Expo mobile app"

Or you point it at a repo that will not start:

stackspirit scan .

It prints a table. Installed, missing, or wrong version. Then the exact command for the OS it detected — macOS, Linux, or Windows. If you pass --fix, it asks y/N before each command. The default is no. If the command needs sudo, the question says so. It will not invent an API key, and it will not run anything while you are reading.

The ghost bit is light on purpose. A missing dependency is "haunting your build." When the machine is fine, it says the machine is quiet. I did not want a Halloween skin on a tool that people will run when they are already stuck.

Demo

On the Linux machine I used while building this, Node 22, Python 3.12, and Go 1.22 were already there. Ollama was not.

stackspirit check "Next.js website" came back quiet and told me to run npx create-next-app@latest. It did not run that for me. create-next-app asks questions, and a tool that starts an interactive installer on its own is not helping.

stackspirit check "AI agent with Google ADK" was the interesting one. Python was new enough (ADK wants 3.11). google-adk was not installed. GOOGLE_API_KEY was not set. The fix was a virtualenv and pip install google-adk, plus a line I have to fill in myself:

export GOOGLE_API_KEY="your-key-here"

stackspirit scan examples/nextjs-site is a folder with a package.json, an .nvmrc of 20, and an empty .env.example. Node 22 was newer than the pin, which the report noted and did not treat as a failure. The real gaps were node_modules and NEXT_PUBLIC_SITE_URL. That is the report I wanted when I clone something and it will not boot.

examples/go-api was quiet. examples/docker-web was not, and the only fix was curl | sudo sh from Docker's own installer, marked as sudo, and not executed.

Code

AlizayAyesha / StackSpirit

Local-first CLI that tells beginners which tools a project needs, using a built-in stack list and a local open model.

StackSpirit

Local-first CLI that tells beginners which runtimes, packages, versions, and API keys a project needs — and which gaps are haunting the build. A built-in knowledge base covers common stacks offline. A local open-weight model explains the rest. Source code never leaves the machine.

Built by Zar Labs.

Repository: https://github.com/AlizayAyesha/StackSpirit

Suggested topics: cli developer-tools beginners toolchain ollama open-source-ai hacktoberfest nodejs typescript

Why

New developers stall before they write anything useful. They want a Next.js site, a Python script that drives a browser, an agent with Google's ADK, or an Expo app, and the repo will not run. Node is too old. python3-venv was never installed. A key is missing. The README assumes a machine that does not look like theirs.

StackSpirit checks the machine first. You say what you want to build, or you point it at a project, and it prints what is installed, what is missing…

View on GitHub

Repo: https://github.com/AlizayAyesha/StackSpirit (MIT licensed)

How I Built It

The part I trust is a built-in list: Node and Next.js, React with Vite, Python, Django, FastAPI, Playwright, Docker, Expo, Flutter, Go, Rust, Google ADK, LangChain, the OpenAI and Anthropic SDKs, and n8n. Versions, packages, env var names, and install commands live in that list. It works with --no-ai, and it works when no model is installed. The samples above were produced that way.

The model has two jobs.

When the sentence is not in the list — "a Hugo site", "a Godot game" — StackSpirit asks a local model to map it. If the model names a stack we already know, we use our commands, not whatever shell line it invented. If it names a new tool, the command has to be boring: one invocation, no pipes, no rm. Anything else is dropped.

When a model is up, it also writes the short "why this matters" paragraph under the table. The table itself stays deterministic. I do not want a model deciding that the install command for Node is something cute.

The default is Ollama and qwen2.5-coder, on 127.0.0.1:11434. You can point the same config at LM Studio, a llama.cpp server, or any other OpenAI-compatible endpoint, including a free model on OpenRouter if that is what you have. The prompt is the stack name, the OS, and rows like "Playwright: missing". File contents and .env values are not in it. I left a sendCode setting in the config so the policy is visible, and the CLI ignores it. There is no mode that uploads the repository.

Why Open Innovation Matters Here

A setup tool learns a lot about a computer. Which languages you have. Which versions. Which keys you have not set yet. That is a map of a beginner's machine, and often of a student's laptop. Sending that map to a hosted API so it can return four sentences is a bad trade.

A local open model is free. It works on a train. I can swap qwen2.5-coder for the next open model without rewriting the CLI. And because the knowledge base is there, the tool still works on a machine that is too new to have a model pulled down — which is, awkwardly, the machine this tool is for.

A closed API would also fail in the exact case I care about: the person is offline, or they have not made an account, or the key they were going to use is the thing they are trying to set up. Open and local is not a slogan here. It is the only setup that does not ask them to be finished before they can start.

Built by Zar Labs (zarlabs.online).

Hacking Ways Into Hacktoberfest 2024:

Alizay Yousfzai — Sat, 12 Oct 2024 02:29:09 +0000

Fueled by Friendship, Code Chaos & Coffee Overload

So here I am, diving headfirst into Hacktoberfest24 all thanks to my friend Yoshi from Sri Lanka, who casually threw me the “you should totally join” & bomb here I am. And just like that, here I am, armed with JavaScript, TypeScript, React, and at least 60 websites worth of frontend genius. Oh, and of course, my beautiful, slightly overworked fingers—which, honestly, deserve their own trophy at this point. (If fingers could have biceps, mine would be ripped.)

Why Hacktoberfest24? Well, Why Not?

I've been slinging code for a while now, jumping between Tailwind, Python, jQuery, and the ever-glorious Next.js—but open-source? That’s like stepping into the dev world’s wild west. It’s chaotic, it’s thrilling, and it’s full of new opportunities to contribute, learn, and maybe bag a few badges. Plus, what’s better than an excuse to code non-stop while downing copious amounts of coffee? It’s practically a developer’s dream diet.

Having already contributed to projects like AtonixCorp, I figured,

Why not crank it up a notch?” Let’s swap bugs for badges, caffeine for sleep, and see if these hands (that have typed 60 websites into existence) can rise to the challenge!

My Blogging Superpower: Making Tech Simple (Even for Grandma):

When I’m not typing away like a coding superhero, I’m over on Medium, breaking down tech so anyone—even my grandma if she was alive may God bless her—can understand it also. Seriously, if I can explain Git in a way that doesn’t make you want to scream into the void or yawn, then we’re all winning here. My goal is simple: tech for everyone, whether you’re a seasoned developer or someone who still thinks ** “Git” is a typo for “gym fit.”**

Hacktoberfest24 Game Plan: Save the Pretty Fingers, Win the Prize:

Now, let’s talk strategy. This being my first Hacktoberfest24, I’ve got a plan. A plan that involves not turning my fingers into mashed potatoes by October 31st. Here’s the deal:

Small but Mighty – You don’t need to rewrite entire codebases. Start with the little things: fix a bug, improve documentation, or tweak that UI. Remember, small PRs can still be mighty.
Polish, Don’t Rush – You've got skills (and fabulous fingers), so aim for quality over quantity. Trust me, maintainers can sniff out a rushed PR like coffee on a Monday morning.
Read the Room (or Repo) – Seriously, read the contributing guidelines before you unleash your coding prowess. Save your elegant fingers from typing up something that’s way off target.
Show Some Love – Hacktoberfest24 is about community, too! Compliment someone’s PR, answer a question, or simply throw some positive vibes into the mix. Your fingers will thank you for the break.

My First Hacktoberfest24: A Journey of Code, Community, and Coffee-Fueled Code Sprints

So here’s the thing—this being my first Hacktoberfest24, I’m beyond excited. I’ve got GitHub notifications on blast, my coffee supply ready, and my fingers working harder than my biceps. (Seriously, have you ever wondered what would happen if fingers had muscles? Finger curls would be a thing, and we’d all be bodybuilders by now.)

But let’s be real, it’s not just about the coding—it's about the community, the chaos, and the caffeine-fueled adventures along the way. Even if I don’t get a badge, at least I’ll come out of this with stronger hands, a few “nice PR!” comments, and the knowledge that I’ve contributed to something bigger than myself.

!!!But I want badges give me badges please...!!!!!

Ready to Contribute? Let’s Hack Together...

Whether you're a Hacktoberfest24 veteran or newbie like me, feel free to check out my GitHub repos! Create issues, drop some pull requests, and I’ll be sure to review and accept them 100% if they're up to snuff (or if you just want some help, I’m here for that too!). I’m all about supporting the community and giving back, so let’s collaborate and make this **Hacktoberfest24 **legendary—together!

Hacktoberfest24: Coding, Coffee & Chain-Smoking Caffeine

To all the *Hacktoberfest24 * Spartans out there: may your PRs get merged, your bugs be minimal, and your coffee cups never run dry! But seriously, with all the caffeine we’re guzzling down to keep our minds awake.

Well I fr wonder some times are we basically chain-smoking for our brains? If so I just hope our minds don’t turn black like smoker’s lungs by the end of this!

Cheers to coding chaos, and more power to the magic of beautiful fingers, and an endless supply of caffeine—see you on the other side of Hacktoberfest24!

Best of luck fellows!!!

Hacking Ways Into Hacktoberfest 2024:

Alizay Yousfzai — Fri, 04 Oct 2024 03:52:27 +0000

Fueled by Friendship, Code Chaos & Coffee Overload

Why Hacktoberfest24? Well, Why Not?

Having already contributed to projects like AtonixCorp, I figured,

Why not crank it up a notch?” Let’s swap bugs for badges, caffeine for sleep, and see if these hands (that have typed 60 websites into existence) can rise to the challenge!

My Blogging Superpower: Making Tech Simple (Even for Grandma):

When I’m not typing away like a coding superhero, I’m over on Medium, breaking down tech so anyone—even my grandma if she was alive may God bless her—can understand it also. Seriously, if I can explain Git in a way that doesn’t make you want to scream into the void or yawn, then we’re all winning here. My goal is simple: tech for everyone, whether you’re a seasoned developer or someone who still thinks ** “Git” is a typo for “gym fit.”**

Hacktoberfest24 Game Plan: Save the Pretty Fingers, Win the Prize:

Now, let’s talk strategy. This being my first Hacktoberfest24, I’ve got a plan. A plan that involves not turning my fingers into mashed potatoes by October 31st. Here’s the deal:

Small but Mighty – You don’t need to rewrite entire codebases. Start with the little things: fix a bug, improve documentation, or tweak that UI. Remember, small PRs can still be mighty.
Polish, Don’t Rush – You've got skills (and fabulous fingers), so aim for quality over quantity. Trust me, maintainers can sniff out a rushed PR like coffee on a Monday morning.
Read the Room (or Repo) – Seriously, read the contributing guidelines before you unleash your coding prowess. Save your elegant fingers from typing up something that’s way off target.
Show Some Love – Hacktoberfest24 is about community, too! Compliment someone’s PR, answer a question, or simply throw some positive vibes into the mix. Your fingers will thank you for the break.

My First Hacktoberfest24: A Journey of Code, Community, and Coffee-Fueled Code Sprints

!!!But I want badges give me badges please...!!!!!

Ready to Contribute? Let’s Hack Together...

Whether you're a Hacktoberfest24 veteran or newbie like me, feel free to check out my GitHub repos! Create issues, drop some pull requests, and I’ll be sure to review and accept them 100% if they're up to snuff (or if you just want some help, I’m here for that too!). I’m all about supporting the community and giving back, so let’s collaborate and make this **Hacktoberfest24 **legendary—together!

Hacktoberfest24: Coding, Coffee & Chain-Smoking Caffeine

Well I fr wonder some times are we basically chain-smoking for our brains? If so I just hope our minds don’t turn black like smoker’s lungs by the end of this!

Cheers to coding chaos, and more power to the magic of beautiful fingers, and an endless supply of caffeine—see you on the other side of Hacktoberfest24!

Best of luck fellows!!!