Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-7Done

1.0.4 GitHub Actions CI (lint + typecheck + build) + README documenting the stack

Estimate: 15m · Depends on: 1.0.2, 1.0.3

Set up GitHub Actions CI in both repos (motir-core and motir-ai) so every pull request gets a green check (or fails fast). For motir-core: three jobs (lint, typecheck, build). For motir-ai: a smaller two-job setup (lint, build) since the service is minimal until Epic 4. Plus write the canonical READMEs.

Why a real README matters more than usual: Motir's planner agent (Epic 4) will inject README.md as context into every subtask prompt. A vague README ("a web app") produces vague output. A specific README ("Next.js 15 App Router + Prisma + Postgres + Tailwind + tRPC v11 + NextAuth v5") gives the coding agent everything it needs to make stack-appropriate choices.

The open-source pitch goes in motir-core's README: "Motir is the open-source PM substrate for AI-native project management. GPL-3.0 licensed. Companion to the closed-source motir-ai planning service." This is the first thing a security-cautious enterprise will read; it should be specific about what's open and what isn't, and link to vision.html principle #19 for the rationale.

What you'll do: In motir-core, create .github/workflows/ci.yml with three jobs running in parallel (lint, typecheck, build); all need Node 20+, pnpm, and the pnpm cache action; build also needs a Postgres service container. Write motir-core/README.md with the structure below (acceptance criteria). In motir-ai, create a smaller CI workflow with two jobs (lint, build) — no DB needed yet. Write motir-ai/README.md declaring it's closed-source, companion to motir-core.

Acceptance criteria

  • motir-core: .github/workflows/ci.yml exists; runs on every PR + push to main; three jobs (lint, typecheck, build) in parallel; Node 20 LTS + pnpm cache; build job has a Postgres service container.
  • motir-ai: .github/workflows/ci.yml exists with two jobs (lint, build); no DB service needed yet.
  • Both repos: CI completes in <3 min on a fresh clone.
  • motir-core README.md has these sections in order:
    • Title + 1-line pitch.
    • Open source — explicit "GPL-3.0; this is the PM substrate. The closed-source planning intelligence ships separately as motir-ai" — with a link to vision.html principle #19.
    • Stack (bulleted: framework, runtime, DB, ORM, auth, styling, tests, deploy).
    • Local setup (3 commands: pnpm install, ./scripts/db-up.sh, pnpm dev).
    • Project layout.
    • Testing.
    • Docs (links to /docs and the discovery tier docs in this very planning corpus).
    • License — name GPL-3.0, link to LICENSE file.
  • motir-ai README.md is short: title, "closed-source AI service — see motir-core for the open-source companion", proprietary license notice, dev-setup commands.
  • README's Stack section is the authoritative reference for every later prompt. Keep it short, specific, link-rich.
  • Open a placeholder PR in each repo; verify CI passes.

Context refs

  • GitHub Actions docs (Node + pnpm setup pattern)
  • package.json — the lint/typecheck/build scripts exist by now
  • docker-compose.yml (from 1.0.2) — for the Postgres service config
  • Project pitch from vision.html hero — to seed the README intro