Check a Ruflo installation for common environment and configuration problems, then run automatic repairs. The checks cover software versions, background services, the memory database, API keys, MCP servers, disk space, and TypeScript.
Run health checks on the Ruflo installation and fix common issues
ruflo-doctor checks a Ruflo installation, diagnoses common problems, and runs automatic repairs. It checks Node.js and npm versions, git, configuration validity, the background service, and the memory database. API keys, MCP servers used to connect external tools, available disk space, and TypeScript are also included in the checks.
Use it after installing Ruflo to check the environment, or when Ruflo is not working as expected and you need to investigate the cause. You can check problem areas together or focus on the memory database, background service, or configuration for a targeted fix.
The skill runs npx @claude-flow/cli@latest doctor --fix. The requirements it checks include Node.js 20 or later and npm 9 or later. Targeted commands include memory init --force, daemon start, and config reset. These operations include database initialization and configuration resets as well as diagnosis.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Run npx @claude-flow/cli@latest doctor --fix to diagnose and auto-repair common issues.
Checks: Node.js 20+, npm 9+, git, config validity, daemon status, memory database, API keys, MCP servers, disk space, TypeScript.
Targeted fixes:
npx @claude-flow/cli@latest memory init --forcenpx @claude-flow/cli@latest daemon startnpx @claude-flow/cli@latest config resetNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.