Core Ruflo MCP tools, commands, and Claude Code orchestration patterns
5 on GitHubby ruvnetv0.2.13MITupdated 5 days agoupstream
/
Plugin ruflo-core from marketplace moaa in ahmadhammoud56/MOAA. Commands read from the repo's manifest — 5 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (5)
discover-plugins
Discover and recommend ruflo plugins based on your workflow, installed MCP tools, and current task
init-project
Initialize a new Ruflo project with MCP tools, hooks, and agent configuration. Use when setting up Ruflo in a fresh repo, or when the user says "init ruflo", "set up ruflo", or asks how to bootstrap the MCP server, hooks, and agent configs from scratch.
ruflo-doctor
Run health checks on the Ruflo installation and fix common issues
ruflo-status
Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation
witness
Sign, verify and track fix-marker regressions over time with an Ed25519 witness manifest. Use when registering fixes or checking a release for regressed fixes. The default seed proves integrity only; set RUFLO_WITNESS_SEED/RUFLO_WITNESS_PUBLIC_KEY for authorship.
Slash commands (2)
/ruflo-core:ruflo-status
Show Ruflo system health, MCP server status, and active agents
/ruflo-core:witness
Manage and verify a tamper-evident fix manifest with temporal history (ADR-103)
Subagents (4)
coder
Implementation specialist for writing clean, efficient code following project patterns
researcher
Pathfinder research specialist — traverses RuVector memory graphs and codebase to surface patterns, dependencies, and prior art
reviewer
Code review specialist for quality, security, and best-practice enforcement
witness-curator
Maintains the tamper-evident witness manifest. Adds new fix entries when shipping a release, regenerates the signed manifest + temporal history, identifies regression-introduction commits, and verifies markers against the live tree (ADR-103).
A four-tier memory ladder for Claude Code where promotion is earned by recurrence, not asserted by confidence. L0 raw transcripts are never injected; L1 candidate atoms are gitignored and recalled on lexical relevance per prompt; L2 project context loads each session start; L3 stable persona is always loaded. L1 to L2 needs three distinct sessions spanning two distinct calendar days (a stated claim needs two; a verified claim is the only single-observation path); L2 to L3 needs two projects and thirty days. Two gates refuse rather than guess: a claim altered by the redaction pass never promotes on evidence alone, and a contradicted claim freezes until a human resolves it. Three hooks run the loop unattended and every one fails open. Nothing reaches a committed CLAUDE.md without an explicit human adopt. Ships 5 stdlib scripts, 3 hooks, a cs-memory-curator agent, /cs-memory, a JSON schema, and a 69-check validator. Concept from TencentCloud/TencentDB-Agent-Memory (MIT); no upstream code included.
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts
Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies. Use for 提 PR / 上游 PR / 贡献代码, "open a PR", "fix this upstream", "rebase against main", "respond to the bot review". Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops).
Assess compliance with the EU General-Purpose AI (GPAI) Code of Practice under the AI Act (Regulation (EU) 2024/1689), Articles 51-56. Covers GPAI model identification (Art. 3(63)), systemic risk model designation (Art. 3(65), Art. 51, 10^25 FLOP training compute threshold), upstream provider obligations under Art. 53 (transparency, technical documentation, copyright policy, training data summary), additional systemic risk obligations under Art. 55 (model evaluation, adversarial testing, AI Office incident notification, cybersecurity), systemic-risk notification and Commission designation under Art. 52, downstream Art. 25 quasi-provider duties, and Art. 53(2) open-source exemption. Built for in-house counsel and AI governance teams reviewing LLM or foundation model deployments, drafting GPAI compliance plans, or assessing systemic risk thresholds. DACH: BaFin, BSI, BNetzA. Pairs with the EU AI Act System Classifier, High-Risk Readiness, FRIA, and Serious Incident Reporting skills.
Research-augmented fork of obra/superpowers. Ships 13 workflow skills (brainstorming, planning, code review, debugging, verification, worktrees, parallel agents) standalone, with no dependency on the upstream superpowers plugin.
13 skills
jamditis/claude-skills-journalism 452
Maintain ruflo-core?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.