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
- 5
- 需求
- 4
- 赞同
- 374
- 已规划
- 4,119
- 已发布
- (motir-core) Any workspace member can remove any other member, the Owner included — `removeMemberAction` checks only "not yourself" and `workspacesService.removeMember` takes no actor at all
- (motir-ai) The Part 1 conversation is told to DERIVE FIRST from the direction docs, the feature catalog and the code graph, but its grounding slice cuts all three and it holds no code tool
- (motir-core) A workspace member who cannot enter a Public project reads its private epics' descendants, and writes watchers, through the in-app member doors
- A container's stored `targetRepo` / `targetRepos` go stale when approve re-derives its repository references — MOTIR-6706 reads back `motir-marketing` while it ships only in `motir-skills`
- A refused merge drops GitHub's own message — 'a setting on the repository blocked it' never says which setting, and nobody can find out
- (motir-ai) The conversation's GATE 1 prescribes search tools the conversation does not hold — `code_search`, and "you owe both" `search_work_items` / `skeleton` / `get_subtree`
- JobWorker.shutdown() returns while the loop's claim query (or a lease renewal) is still running — a claim can land after the release and hold rows for a stopped worker
- (motir-skills) The two-mode `motir-fix-bugs` skill — runbook mode routes to `prompts/fix-bugs.md`; standalone mode condenses the population, the three terminating dispositions and one PR per bugMotir 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 FIX-BUGS protocol — `prompts/fix-bugs.md` + `prompts/fix-bugs.py next`: the Bugs folder's own `todo` bugs, one at a time, three terminating dispositions, one PR per bugMotir 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
- Fix the Bugs folder — the fix-bugs protocol in the runbook and the two-mode `motir-fix-bugs` 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-ai) `creditLaneGate`'s two regression-seam tests loop every shipped planning rate under vitest's default 5 s timeout, so they time out on a loaded runner
- (motir-skills) The two-mode `motir-run` skill — runbook mode routes into `run.md`; standalone mode condenses the close-out sweep, claim, branch-per-card, one PR, status walk, How to test, out-of-scope bugs, and the no-`motir-plan` fallbackMotir 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-skills) Scaffold the public skills repository — README, the two-mode SKILL.md shape, the sync-metadata format, plugin-marketplace manifests and a CI validator — and ship `motir-mark` and `motir-log-bug` in 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's skills in a public repository — `motir-run`, `motir-log-bug` and `motir-mark` as two-mode skills 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-ai) The Part 1 conversation composes the `core` pack whole, so its system prompt names tools it does not hold — and one rule tells it `web_search` "is on your tool surface"
- (verification) On the live tenant, a run without `motir-plan` submits its correction to the hosted planner — and with a token lacking `ai:plan` it parks, comments and stopsMotir 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
- (manual) Create the public `moooon-B-V/motir-skills` repository (MIT, `main` protected) and connect it to the MOTIR project's repository setMotir 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 Visitor consent screen at `app.motir.co/p/<identifier>/consent` — it says the reader's name and email will be visible to the project's Managers, Continue records the consent and returns to the view they asked for, Go back leaves without a recordRoles & 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) A person's own visitor records in their account data export — which public projects they consented to share their name and email with, and whenRoles & 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) The project's Visitors, for its Managers — a Visitors section on Settings › Access & members listing each visitor's name, email, first and latest visit and consent time, newest first and paged, behind `project:manage_access`Roles & 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