marin-community

Build, validate, publish, update, inspect, query, roll back, or archive a dynamic Marina applet. Use for Artifact+-style web apps that should run behind Marina authentication, carry small bundled assets or data, use an applet-owned Postgres schema, or add a…

Review an explicitly identified Marin pull request against the repository's correctness and maintainability expectations.

Search or cite Echo when Marin's prior-work policy applies, another selected workflow requires it, or the user explicitly asks; do not substitute it for local code search.

Publish a tagged Echo record after every incident, then link its canonical URL from the associated pull request or issue.

Refresh a named Marin external fork pin onto a newer upstream base using its configured descriptor and required end-to-end test.

Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.

Use only when a change is ready to commit, push, or open or update its pull request; do not activate during implementation.

Run the read-only infra/lint PR reporter only when invoked by CI or explicitly requested; do not select it for the commit workflow's fix-and-respond review.

Initialize and run a focused RL operations session across Iris and explicitly selected supported backends: inventory jobs, dispatch diagnosis, perform authorized lifecycle actions, and maintain a reproducible handoff for an explicit list of experiment…

Lint, run the pre-PR checks, commit, push, and author or update the branch's pull request in the required plain-text format. Use when committing, pushing, or creating/updating a PR.

Search and cite Marin's shared Echo wiki, repository index, issues, pull requests, and optional Discord history. Use when prior cross-project decisions, incidents, workflows, exact errors, or reusable knowledge could inform a task, and before adding or…

Debug code bugs and operational faults while recording distilled hypotheses, evidence, and outcomes in Marin's shared Echo work log.

File a GitHub issue for a bug or improvement found this session.

Maintain a cross-project task or research log in Echo. Use for multi-step investigations, experiments, long-running implementation work, or any task whose milestones must survive the current agent session without adding a repository logbook file.

Publish or revise a concise cross-project design proposal in Echo. Use for an explicit design task or a design-level change whose context, decision, interfaces, tradeoffs, and rollout need review without adding a repository design document.

Publish a durable debugging or infrastructure incident record to Echo. Use when a multi-step investigation reaches a conclusion, a failure needs a postmortem, or a recovery pattern should be visible across Marin projects.