Repository navigation
squad- workflows seem to assume a particular project type? #87
Description
I added squad to an existing codebase that already had deployment in place. It generated a bunch of workflows (squad-release, etc) that seemed to generally assume I was building an npm package (I wasn't) and that I had a package.json in the root (I don't). I didn't dig in yet to see if these were AI generated (so it could be told to look at the existing code and workflows) or just part of the original install command. But either way, feels like it could be tweaked.
Activity
bradygaster commentedon Feb 16, 2026
Would be interested in what you think could be tweaked; I did update the docs to reflect that we're doing these workflow injections. This was an omission on my part in the docs; thanks!
tlmii commentedon Feb 16, 2026
Yeah, given that its part of the initial command, I'm not sure. Depends on your long-term intent with the way things get installed, I guess. And also on how "required" those workflows are for squad to keep going.
You could detect that there is an existing file structure (e.g. the tool is not being run in an empty folder, there's a .github/ folder, etc) and ask if it should install the workflows. Maybe a subset is still relevant?
docs(ai-team): issues 86/87 analysis for v0.5.0
feat: detect project type and generate workflow stubs for non-npm pro…
docs(ai-team): Log issues #86 & #87 completion
feat: project type detection and git safety rules (#123)
bradygaster commentedon Feb 20, 2026
Fixed in PR #123 (merged to dev). Squad now detects project type (npm, go, python, java, dotnet) and generates workflow stubs with TODO comments for non-npm projects instead of broken npm commands.