core-lead/molecule-core
1
0
Fork 0
forked from molecule-ai/molecule-core
Code Pull Requests Activity
39179dfcb3
molecule-core/plugins/molecule-workflow-retro/commands/retro.md
Hongming Wang 119b02c544 feat(plugins): split guardrails into 12 modular plugins 
Replaces the proposed monolithic molecule-guardrails plugin with 12
single-purpose plugins users can install à la carte. Powered by a
small extension to the AgentskillsAdaptor base class so any plugin can
ship hooks/, commands/, and a settings-fragment.json without writing a
custom adapter.

## Base adapter changes

workspace-template/plugins_registry/builtins.py + sdk/python/molecule_plugin/builtins.py
(both copies — drift-tested):
- New _install_claude_layer() helper called at the end of install()
- Conditionally copies hooks/ → /configs/.claude/hooks/ (preserving exec bit)
- Conditionally copies commands/*.md → /configs/.claude/commands/
- Conditionally merges settings-fragment.json into /configs/.claude/settings.json
  with ${CLAUDE_DIR} placeholder rewritten to the workspace's absolute install
  path. Existing user hooks are preserved (deep-merge by event name).
- All steps no-op when the plugin doesn't ship the corresponding files,
  so existing skill+rule plugins (molecule-dev, superpowers, ecc,
  browser-automation) are unchanged.

Drift test (tests/test_plugins_builtins_drift.py) still passes.

## 12 new plugins

Hook plugins (ambient enforcement):
- molecule-careful-bash       — refuses destructive bash; ships careful-mode skill
- molecule-freeze-scope       — locks edits via .claude/freeze
- molecule-audit-trail        — appends every Edit/Write to audit.jsonl
- molecule-session-context    — auto-loads cron-learnings at session start
- molecule-prompt-watchdog    — injects warnings on destructive prompt keywords

Skill plugins (on-demand):
- molecule-skill-code-review        — 16-criteria multi-axis review
- molecule-skill-cross-vendor-review — adversarial second-model review
- molecule-skill-llm-judge          — deliverable-vs-request scoring
- molecule-skill-update-docs        — post-merge doc sync
- molecule-skill-cron-learnings     — operational-memory JSONL format

Workflow plugins (slash commands):
- molecule-workflow-triage  — /triage full PR-triage cycle
- molecule-workflow-retro   — /retro + cron-retro skill, weekly retrospective

Each ships only what it needs — most have just plugin.yaml + skills/ or
hooks/ + adapter (one-line stub: `from plugins_registry.builtins import
AgentskillsAdaptor as Adaptor`). Total ~120 files but each plugin is
small and self-contained.

## Verification

- python3 -m molecule_plugin validate plugins/molecule-* → all 13 valid
  (12 new + pre-existing molecule-dev)
- End-to-end install smoke test on representative samples: hook plugin
  (molecule-careful-bash), skill-only plugin (molecule-skill-code-review),
  workflow plugin (molecule-workflow-triage). All produce expected
  /configs/ tree, settings.json paths rewritten, exec bits preserved,
  zero warnings.
- workspace-template pytest tests/test_plugins_builtins_drift.py → passes
  (SDK + runtime stay in sync).

## CLAUDE.md repo-doc updated

Lists all 12 new plugins under the existing Plugins section, organized
by category (hook / skill / workflow). Each entry one line, recommend-
together hints where dependencies make sense.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-14 12:20:04 -07:00

1.5 KiB
Raw Blame History

name description
retro Generate a weekly retrospective digest — PRs merged, gate failures, code-review severity trend, time-to-merge, issues picked up. Posts as a GitHub issue.

/retro

Weekly retrospective on cron + agent activity. Default cadence: Sundays 23:00 local. Manual invocation on demand.

Steps

  1. Compute over the prior 7 days:

    • Merged PR count (total + by category)
    • Issues closed (with PR-link for each)
    • Time-to-merge: median, p90, max — exclude docs PRs
    • Gate failure breakdown (which gates, how often)
    • Code-review findings: total 🔴/🟡/🔵, trend vs prior week
    • Mechanical fixes pushed (count)
    • Skips by reason: design-judgment / CI-down / scope-too-open / noteworthy-CEO-needed
    • Code volume: net LOC added/removed
    • Test count delta (Go + Python + Vitest + Jest)
    • New runtime / library / tool added or removed

  2. Format per the cron-retro skill template.

  3. Post as a new GitHub issue titled Cron retro: <start> → <end> (week N) with labels meta, retro.

  4. If trends are bad (gate failure rate up, 🔴 findings appearing, time-to-merge >50% increase), flag prominently in the body and @-mention the workspace owner.

  5. Skip new-issue creation if the prior 7 days had < 3 merged PRs; post a one-liner in the latest weekly retro issue's comments instead.

Standing rules

  • careful-mode applies — don't mass-close stale issues, don't delete prior retros
  • The retro is observational, not actionable — propose 2-3 follow-ups for the user but never auto-create them