Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

murmur-curate-learnings

Sterne7

Forks0

Aktualisiert11. Juli 2026 um 01:55

Promote mature Murmur learnings journal entries into an agent's binding Recurring patterns. Use when the user asks to curate lessons, promote repeated learnings, or names an agent learnings file under `.codex/learnings/`.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

murmur-io

murmur-io/murmur

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	murmur-curate-learnings
description	Promote mature Murmur learnings journal entries into an agent's binding Recurring patterns. Use when the user asks to curate lessons, promote repeated learnings, or names an agent learnings file under `.codex/learnings/`.

Murmur Curate Learnings

Curate the compounding-lessons loop for one agent. The expected input is an agent name that maps to .codex/learnings/<agent>.md.

Steps

Validate the requested agent exists under .codex/learnings/. If unknown, list valid agents and stop.
Read .codex/learnings/<agent>.md and scan ## Run journal for entries with Status: journal.
Find lessons that recur: two or more journal entries pointing at the same failure mode, or one entry the operator confirms is load-bearing.
For each promotion, add one tight imperative bullet to ## Recurring patterns. Match the existing terse style and keep the section to about 20 bullets; if full, merge or drop the weakest existing bullet and say which.
Mark each source journal entry **Status:** distilled (<today>), using date +%F.
Do not invent lessons that are not in the journal.
Report which bullets you added or merged and which journal entries you marked distilled.

Mehr aus diesem Repository

gleiches Repository

harness

murmur-io/murmur

Run a change through the full Murmur harness — isolated worktree, writer, deterministic checks, independent adversarial + risk reviews, hash-bound PASS attestation, guarded commit. Use PROACTIVELY when a change is risky, multi-step, or you want the earned safety net (lock/crypto/egress/protocol, or anything you want independently verified). Skip it for docs, chores, and low-risk edits — those commit normally.

2026-07-247

release-murmur

murmur-io/murmur

Cut a signed, notarized macOS release of Murmur (Tauri 2 + Angular 22). The exact, proven step-by-step runbook — preflight gates → version bump (+ Cargo.lock sync) → QueaT commit → PR-merge to the `murmur` trunk (never direct-push) → rustup targets → stop dev → universal build → Developer-ID sign BY IDENTITY HASH (the Polish-ń cert gotcha) → DMG → notarize → staple/spctl → gh release create + upload. Use whenever the user wants to ship, release, cut a version, build a distributable .app/.dmg, sign/notarize, or publish a GitHub release of Murmur. Supersedes the stale docs/RELEASE-CHECKLIST.md.

The agentic feature-shipping discipline for Murmur (Tauri 2.11 Rust core + Angular 22 zoneless). Scope → (Workflow) plan → build backend and/or FE under the project conventions → ADVERSARIAL verify (an adversarial-verifier pass, plus a lock-security review when the change touches the lock/crypto/visibility path) → gates green (cargo test --lib, ng lint, ng build, scripts/ci.sh) → QueaT commit → PR to the `murmur` trunk. Use whenever the user wants to build, implement, add, or ship a feature/fix in Murmur end-to-end. Encodes the verify-before-trust discipline that caught 7 bugs.

2026-07-237

tauri-dev

murmur-io/murmur

Run and iterate Murmur locally (Tauri 2.11 + Angular 22 zoneless). The exact dev-run recipe — MURMUR_DEV_DEK/MURMUR_DEV_KEK to avoid keychain prompts, source ~/.cargo/env, ng on :1420 + MCP on :8765, the `cargo test --lib`-not-`clippy --all-targets` inner loop, owner-aware clean relaunch, and reading the boot/abort log. Use whenever the user wants to start/run/serve Murmur in dev, debug a launch/abort, relaunch cleanly, or run the Rust test loop.

name	murmur-curate-learnings
description	Promote mature Murmur learnings journal entries into an agent's binding Recurring patterns. Use when the user asks to curate lessons, promote repeated learnings, or names an agent learnings file under `.codex/learnings/`.

Murmur Curate Learnings

Curate the compounding-lessons loop for one agent. The expected input is an agent name that maps to .codex/learnings/<agent>.md.

Steps

Validate the requested agent exists under .codex/learnings/. If unknown, list valid agents and stop.
Read .codex/learnings/<agent>.md and scan ## Run journal for entries with Status: journal.
Find lessons that recur: two or more journal entries pointing at the same failure mode, or one entry the operator confirms is load-bearing.
For each promotion, add one tight imperative bullet to ## Recurring patterns. Match the existing terse style and keep the section to about 20 bullets; if full, merge or drop the weakest existing bullet and say which.
Mark each source journal entry **Status:** distilled (<today>), using date +%F.
Do not invent lessons that are not in the journal.
Report which bullets you added or merged and which journal entries you marked distilled.