moooon
Motir
Vibe the 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
- 6
- requests
- 4
- upvotes
- 488
- planned
- 5,024
- shipped
- Error: aborted
- (motir-marketing) `/docs/skills` gains the `motir-fix` usage section, the install commands move to its release tag, and the page E2E covers the new sectionMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-meta) Pin the `motir-skills` release that carries `motir-fix` — bump `PUBLIC_SKILLS`, add the skill to its list, and prove `install.sh` and the drift guard passMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (deploy) Release `motir-skills` with `motir-fix` — bump `plugin.json`, tag the next minor, publish the GitHub release, then install it from the tag as a consumer wouldMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- `motir-fix` ships — the next `motir-skills` release carries it, motir-meta pins that release, and /docs/skills documents itMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-core · design) The app's SERVER-ERROR page, drawn — a page that failed inside the shell, the whole signed-in shell failing, and the root failing: what the reader is told, Retry and the way out, in light and dark
- (motir-core) A plain workspace member can REPLACE the workspace's GitLab credential — `completeOAuthCallback` checks no role, and the upsert overwrites the existing connection with the member's own GitLab account and token
- (motir-core) Design — `/ready` grouped: runnable-container rows that expand to their ready leaves, standalone leaf rows, and a separate Bugs list (`ready--lanes.mock.html` delta)
- (motir-skills) The two-mode `motir-fix` skill — runbook mode routes to `prompts/fix.md`; standalone mode condenses the claim, the checkout on the pull requests' own branches, liveness, the CI-fix loop, the acceptance re-run and the closeMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-meta) The REPAIR protocol — `prompts/fix.md`: claim one card's repair, check out its pull requests' own branches, keep the repair alive, fix by `run.md`'s CI-went-red rule, re-record a sent-back acceptance, close with the outcome, reportMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (verification) The three repair tools are LIVE on app.motir.co — `tools/list` names them, and a claim → touch → close round trip works on a scratch card, with `taken` refused across MCP and CLIMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- Repair a red card from your own agent — confirm the repair tools live, then the repair protocol in the runbook and the two-mode `motir-fix` skill on `motir-skills` `main`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-marketing) CI on `main` has been red on every push since 2026-09-03 — the deploy's smoke check reads `motir-marketing.fly.dev`, which the host router sends to its 404 room, although the release itself succeeds
- (motir-core · test) Story integration gate — the three repair tools through the real MCP transport: parity with the REST claim, `taken` across MCP and REST, every refusal, liveness past the five-minute rule, close, permissions and cross-tenant isolationMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-core) The MCP door onto the REPAIR CLAIM — `claim_work_item_repair`, `touch_work_item_repair` and `close_work_item_repair` over the shipped `workItemRepairService` and dispatch-run close, gated `work_item:edit`, documented in `docs/mcp.md`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- Agents claim, keep alive and close a red card's repair over the MCP — `claim_work_item_repair`, `touch_work_item_repair` and `close_work_item_repair`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (verification) Read production after MOTIR-6171 ships — motir.co's old read links 308 into the app and land on sign-in, the sitemap lists no read page, a customer-owned address redirects the same way where one exists, and the public contract serves its five deprecated operations still answeringRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- public-api-conventions.md §3 still says REST v1 authorizes by TokenScope — v1 routes require a permission since MOTIR-2576
- (motir-core) The members' Triage inbox is renamed Requested features — the sidebar entry, the page heading and its address, the permission's label in the role editor, and every member-facing string that names the queue, in en and zh, with the old /triage address still landing a bookmarkRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) E2E + acceptance video — a consented Visitor opens Requested features, sees pending requests by votes with names only, upvotes one, reloads and still sees it voted, undoes it, and meets no Manager action or the word "triage"; a member lands in their own Requested features inboxRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do