Evan d215388039 feat(devops): add auto-evolution loop (PR review + BMAD pipeline) (#94)
* feat(devops): add auto-evolution loop (PR review + BMAD bug/feature pipeline)

Extends the DevOps Hand to periodically scan configured GitHub repos and:
- review open PRs via the existing code-reviewer sub-agent, posting a
  single COMMENT review back to GitHub (never auto-APPROVE)
- triage open issues via labels first, single-prompt LLM fallback
- dispatch actionable issues (bug-fix / feature) to a new implementer
  sub-agent which runs the BMAD pipeline (Brainstorm -> Architect ->
  PRD -> Implement) scaled by bmad_strictness and produces a DRAFT PR

Safety floor (always on):
- draft PRs only, never auto-ready, never merge
- never push to main/master/protected branches
- escalates to devops_queue.json when touching workspace Cargo.toml,
  migrations, secrets, or >30 changed files
- 70% per-turn token budget cap so subsequent ticks have headroom

New settings: auto_evolve, evolution_repos, evolution_check_interval,
bmad_strictness. New sub-agent: agents.implementer. New SKILL.md
sections: Issue Triage Playbook, PR Review Automation, Bug Fix
Playbook, BMAD Feature Pipeline, Draft PR Creation. Three new
dashboard metrics: prs_reviewed, issues_processed, draft_prs_opened.

* fix(devops): address PR review — close blocking + medium + style issues

Blocking (5):
- add max_changed_files setting (was referenced in implementer prompt
  but never defined)
- drop metering_query reference (tool isn't in tools = [...] list);
  agent self-paces against budget instead
- fix \n\n literal in jq --arg for issue cross-link comment; compose
  body in shell with printf so newlines survive
- resolve BASE_BRANCH via /repos/owner/repo .default_branch instead
  of relying on an undefined variable
- complete reviewer-verdict → GitHub review-event mapping (4 cases,
  not just request_changes); block routes through REQUEST_CHANGES
  with a blocking-prefix in the body, approve downgrades to COMMENT

Medium (5):
- correct Phase 6 → Phase 7 in the auto-evolution settings comment
- remove schedule_create busy-loop confusion; Phase 7 fires per-turn
  while the Hand is already frequency = "continuous", with cadence
  enforced via devops_evolution_cursor memory key
- generalize the forbid-main-worktree wording — discover and honor
  whatever pre-commit / pre-push / commit-msg hooks the upstream
  repo configures (was librefang-specific)
- clarify the AI-attribution rule: ban LLM-vendor attribution
  (Claude, GPT, 🤖, etc.) but allow process attribution
  (DevOps Hand → implementer) for traceability
- add USER_TYPE = "Bot" short-circuit that was extracted but never
  applied (bots get a token-cheap skip, not a deep review)

Style (2):
- document the four event_publish event names (devops_evolution_*)
  in a new SKILL.md table alongside the memory-keys table
- justify implementer's max_history_messages = 100 with a comment
  (BMAD 4 phases × cargo build/test chains needs headroom)

* docs(devops): tighten evolution snippets (D1-D4 second-review nits)

D1 -- show SUMMARY_BODY (and VERDICT) assignment in PR review snippet:
add explicit jq -r .summary / .verdict extraction from reviewer_output.json
so the agent reading SKILL.md doesn't have to infer where these come from.

D2 -- reword strict-mode wait semantics in both HAND.toml and SKILL.md:
'Stop. Wait...' was misleading because the agent loop has no in-turn
pause primitive. Now spells out: end the current turn after queueing,
let the continuous tick re-read the queue, resume on approved / skip
on pending / abandon on rejected. Explicitly forbids busy-wait and
sleep loops.

D3 -- restructure bot / huge-diff short-circuit so agent-tool calls are
expressed as numbered agent steps, not as '# memory_store ...' comments
inside a bash block. The bash block now only extracts cheap signals;
the decision and the tool calls are clearly agent-level.

D4 -- remove the misleading 'exit 0' from the short-circuit bash and
add a one-liner noting that exit 0 inside shell_exec only ends one
shell session, not the Phase 7 pass; the agent must choose to move on.
2026-05-14 15:54:42 +09:00

LibreFang Registry

Community-maintained content registry for LibreFang — the open-source Agent Operating System.

This repository is the single source of truth for all installable content definitions. Anyone can submit a PR to add new agents, hands, MCP servers, skills, or provider models — no changes to the LibreFang binary required.

Overview

Type Count Description
Hands 14 User-facing "apps" — agent + tools + settings + dashboard
Agents 32 Autonomous agent definitions with model config and tools
MCP Servers 25 MCP server connections (GitHub, Slack, DBs, etc.)
Providers 46 LLM provider & model metadata with pricing
Models 232 Individual model definitions across all providers
Aliases 70 Short names mapped to canonical model IDs
Plugins 10 Memory, guardrails, and conversation plugins
Skills 2 Reusable prompt templates and Python scripts
Workflows 9 Pre-built multi-agent workflow definitions
Templates 6 Starter templates for each content type

Repository Structure

librefang-registry/
├── agents/                # Agent definitions (TOML manifests)
│   ├── hello-world/
│   │   └── agent.toml
│   ├── researcher/
│   │   └── agent.toml
│   └── ...                (32 agents)
├── hands/                 # Hand definitions (app bundles)
│   ├── browser/
│   │   ├── HAND.toml      # Metadata, tools, settings, i18n (6 languages)
│   │   └── SKILL.md       # Domain expert knowledge injected at runtime
│   ├── trader/
│   │   ├── HAND.toml
│   │   └── SKILL.md
│   └── ...                (14 hands)
├── mcp/                   # MCP server templates
│   ├── github.toml
│   ├── slack.toml
│   └── ...                (25 MCP servers)
├── providers/             # LLM provider & model metadata
│   ├── anthropic.toml
│   ├── openai.toml
│   └── ...                (46 providers, 232 models)
├── plugins/               # Memory, guardrails, and utility plugins
│   ├── episodic-memory/
│   ├── guardrails/
│   └── ...                (10 plugins)
├── skills/                # Reusable skill definitions
│   ├── custom-skill-prompt/skill.toml
│   └── custom-skill-python/
├── workflows/             # Pre-built multi-agent workflow definitions
│   ├── code-review.toml
│   ├── research.toml
│   └── ...                (9 workflows)
├── templates/             # Starter templates for each content type
│   ├── agent.toml
│   ├── HAND.toml
│   └── ...                (6 templates)
├── docs/                  # Additional documentation
│   └── content-guide.md   # Content contribution guidelines
├── aliases.toml           # Global model alias mappings (70 aliases)
├── schema.toml            # Provider/model schema reference
├── scripts/
│   └── validate.py        # Content validation script
├── CONTRIBUTING.md
└── LICENSE                # MIT

Content Types

Hands

Hands are the user-facing "apps" in LibreFang. Each hand bundles an agent, tools, user-configurable settings, dashboard metrics, dependency checks, and i18n translations into a single deployable unit.

Every hand includes a SKILL.md — domain-specific expert knowledge that is injected into the agent's context at runtime, giving it deep expertise in its domain.

Icon Hand Category Description
📈 analytics data Data collection, analysis, visualization, dashboards, and automated reporting
🔌 apitester development Endpoint discovery, request validation, load testing, and regression detection
🌐 browser productivity Web navigation, form filling, and multi-step web tasks with user approval
🎬 clip content Turns long-form video into viral short clips with captions and thumbnails
🔍 collector data Intelligence collection, change detection, and knowledge graphs
👷 devops development CI/CD management, infrastructure monitoring, deployment, and incident response
📊 lead data Lead generation, enrichment, scoring, and scheduled delivery
💼 linkedin communication Profile optimization, content creation, networking, and engagement
🔮 predictor data Signal collection, calibrated predictions, and accuracy tracking
📢 reddit communication Subreddit monitoring, content posting, and engagement tracking
🧪 researcher productivity Deep research, cross-referencing, fact-checking, and structured reports
🎯 strategist productivity Market research, competitive analysis, and strategic planning
📈 trader data Multi-signal analysis, adversarial reasoning, and risk management
𝕏 twitter communication Content creation, scheduled posting, engagement, and analytics

HAND.toml format:

id = "browser"
name = "Browser Hand"
description = "Autonomous web browser"
category = "productivity"
icon = "🌐"
tools = ["browser_navigate", "browser_click", "browser_type"]

[routing]
aliases = ["browse", "open website"]
weak_aliases = ["web", "url"]

[[requires]]
key = "chromium"
requirement_type = "binary"
check_value = "chromium"

[[settings]]
key = "headless"
setting_type = "toggle"
default = "true"

[agent]
name = "browser-hand"
module = "builtin:chat"
system_prompt = """You are an autonomous web browser agent..."""

[dashboard]
[[dashboard.metrics]]
label = "Pages Visited"
memory_key = "pages_visited"
format = "number"

# i18n — 6 languages supported: zh, ja, ko, es, fr, de
[i18n.zh]
name = "浏览器 Hand"
description = "自主网页浏览器"
category = "生产力"

[i18n.zh.settings.headless]
label = "无头模式"
description = "在后台运行浏览器"

Agents

Agent definitions describe autonomous agents with model configuration, tools, capabilities, and routing aliases.

name = "hello-world"
description = "A friendly greeting agent"
module = "builtin:chat"

[model]
provider = "default"
model = "default"
system_prompt = "You are a helpful assistant."

[capabilities]
tools = ["web_search", "file_read"]

32 built-in agents: academic-researcher, analyst, architect, assistant, code-reviewer, coder, customer-support, data-scientist, debugger, devops-lead, doc-writer, email-assistant, health-tracker, hello-world, home-automation, legal-assistant, meeting-assistant, ops, orchestrator, personal-finance, planner, recipe-assistant, recruiter, researcher, sales-assistant, security-auditor, social-media, test-engineer, translator, travel-planner, tutor, writer

MCP Servers

MCP server templates define MCP server connections with transport configuration, required environment variables, and setup instructions.

id = "github"
name = "GitHub"
category = "devtools"

[transport]
type = "stdio"
command = "npx"
args = ["-y", "@modelcontextprotocol/server-github"]

[[required_env]]
name = "GITHUB_PERSONAL_ACCESS_TOKEN"
is_secret = true

25 MCP servers across 6 categories:

Category MCP Servers
DevTools bitbucket, github, gitlab, jira, linear, sentry
Data elasticsearch, mongodb, postgresql, redis, sqlite
Productivity dropbox, gmail, google-calendar, google-drive, notion, todoist
Communication discord, slack, teams
Cloud aws, azure, gcp
AI Search brave-search, exa-search

Providers

Provider files define LLM providers and their models with pricing, context windows, and capability flags. See schema.toml for the full field reference.

49 providers including: Anthropic, OpenAI, Google Gemini, DeepSeek, Groq, Mistral, Cohere, xAI, Together, Fireworks, Ollama (local), LM Studio (local), vLLM (self-hosted), Alibaba Coding Plan, and many more.

339 models with metadata for each: pricing (input/output per token), context window size, capability flags (vision, function calling, streaming), and tier classification.

Aliases

Global model alias mappings in aliases.toml let users reference models by short names:

"sonnet" = "claude-sonnet-4-6"
"gpt4" = "gpt-4o"
"flash" = "gemini-2.5-flash"
"deepseek" = "deepseek-chat"

Models can also define aliases directly in their provider TOML files, which are auto-registered at load time.

Plugins

Plugins extend agent capabilities with memory systems, safety guardrails, and conversation utilities.

10 plugins: auto-summarizer, context-decay, conversation-logger, episodic-memory, guardrails, keyword-memory, sentiment-tracker, todo-tracker, topic-memory, user-profile

Skills

Reusable prompt templates or Python scripts that agents can invoke.

[skill]
name = "meeting-agenda"
description = "Generate a structured meeting agenda"

[runtime]
type = "promptonly"

[prompt]
template = "Create a meeting agenda for: {{topic}}"

Workflows

Pre-built multi-agent workflow definitions in workflows/<name>.toml orchestrate multiple agents for complex tasks.

9 workflows: brainstorm, code-review, content-pipeline, content-review, customer-support, data-pipeline, research, translate-polish, weekly-report

Templates

Starter templates in templates/ for creating new content. Copy a template to get started quickly:

cp templates/agent.toml agents/my-agent/agent.toml
cp templates/HAND.toml hands/my-hand/HAND.toml

6 templates: agent.toml, HAND.toml, integration.toml, plugin.toml, provider.toml, skill.toml

See also docs/content-guide.md for naming conventions and contribution guidelines.

Usage

Install from Registry

# Update all registry content
librefang catalog update

# Install a specific hand
librefang hand install browser

# Install a specific MCP server
librefang mcp install github

Custom Local Content

Create custom content locally without submitting to this registry:

# Custom agent
mkdir -p ~/.librefang/agents/my-agent
# Edit ~/.librefang/agents/my-agent/agent.toml

# Custom model aliases
# Add to ~/.librefang/model_catalog.toml

Validation

python scripts/validate.py

Validates all content files for correctness: required fields, valid types, non-negative costs, no duplicate IDs.

Contributing

  1. Fork this repository
  2. Add or edit content in the appropriate directory
  3. Run validation: python scripts/validate.py
  4. Submit a Pull Request

See CONTRIBUTING.md for detailed instructions for each content type.

License

MIT License. See LICENSE.

S
Description
Arka mirror of the LibreFang community content registry — agents, hands, integrations, skills, and provider models. Mirrored from github.com/librefang/librefang-registry.
Readme MIT
1.7 MiB
0 Stars 1 Watchers 0 Forks
Languages
Python 88.5%
JavaScript 7.6%
Makefile 3.6%
Shell 0.3%