eric-tramel/moraine

moraine

Search and inspect prior agent sessions, observe active agent work, or prepare a sanitized Moraine bug report through the local Moraine MCP server.

release

Cut and publish Moraine releases from a version argument such as /release X.Y.Z in Kiro or a request to use $moraine-dev:release in Codex. Use when Codex or Kiro is asked to run Moraine's release process, bump release-managed versions, create and merge the…

code-review

Coordinate a delegated full multi-persona code review for a Moraine PR or local change. Use when asked to review a PR, run review agents, get code review feedback, or iterate on review feedback using all CodeReview personas: elegance, idiom, correctness,…

moraine-author-pr

Create Moraine pull requests on GitHub. Use when the branch is ready to open a PR; when the user asks to create, push, or open a PR; after local changes are committed; or when documenting user-facing features, bug fixes, performance optimizations, validation,…

moraine-start-work

Start Moraine repository development work safely. Use when an agent takes on new code, docs, test, CI, packaging, or release work in this repo; when it must create or verify an isolated branch/worktree; when sibling agent collisions are possible; or before…

agent-smoke-e2e

End-to-end smoke check of the moraine MCP server. Exercises the public retrieval workflow against a live moraine stack and prints a PASS/FAIL matrix.

realtime-peek

Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.

session-search

Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.

moraine-sandbox-qa

Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for…

bug-report

Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

realtime-peek

Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.

session-search

Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.

code-review-completeness

Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.

code-review-correctness

Review a PR through the CodeReviewCorrectness persona. Use when asked to check whether the implementation does the job correctly, avoids bugs and regressions, preserves data and API contracts, handles relevant edge cases, and has tests that would catch the…

code-review-elegance

Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of…

code-review-idomatic

Review a PR through the CodeReviewIdomatic persona. Use when asked to check whether code is idiomatic for the implementation language, follows standard library and ecosystem conventions, avoids unnecessarily novel implementations, and matches established…

code-review-scope

Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear.

code-review-security-review

Review a PR through the CodeReviewSecurityReview persona. Use when asked to check whether code is safe, avoids backdoors, vulnerable dependencies, injection attacks, auth bypasses, secret leaks, unsafe file/network behavior, and other security regressions.

code-review-yagni

Review a PR through the CodeReviewYAGNI persona. Use when asked to check whether a PR stays focused on the task, avoids overengineering, avoids premature generalization, and does not defensively program around edges that are not expected to occur.

crystallize

Turn a rough feature, bug, refactor, architecture, documentation, or operations idea into a ready-to-implement local plan file. Use when the user asks to crystallize, shape, refine, plan, spec, or de-risk ambiguous work before implementation; the workflow…

release-notes

Rewrite a moraine GitHub release body in the house format — one-sentence pitch, install block, usage-focused "what's new" sections with PR links and optional screenshots, a platform-support table, upgrade notes, and a single deduped auto-generated changelog…