Evan
7881d327a5
* refactor: migrate icon fields from emoji to lucide:<name> tokens
Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:
- Emoji render very differently across OS/browser/font stacks; the
registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
their icons stored as literal Python-style escape strings
("\\U0001F3AC") because the TOML parser upstream never decoded
them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
[i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
up correctly.
87 files touched. example manifests left untouched (still "TODO").
* fix: backfill i18n name + drop the single-member email category
- Every existing [i18n.<lang>] block now has a `name` field. 60 files
previously translated description but kept the English name
implicitly — which rendered as "some English some Chinese" in the
registry UI. Fill in the missing name from the English brand (or a
known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
reclassify it as "messaging" so the sub-category filter chip list
on the category page isn't littered with singletons.
* feat(i18n): localize 76 agents/integrations/plugins into 7 languages
Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.
Coverage:
- 32 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)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
brand names kept as-is across all locales, only descriptions
translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
episodic-memory, guardrails, keyword-memory, mempalace-indexer,
sentiment-tracker, todo-tracker, topic-memory, user-profile)
The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.
* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam
Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.
- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
were already present). Brand names kept as-is in all locales so users
recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
translation mirrors the existing zh one in structure and tone so the
catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
(zh-TW, de, es, fr).
Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
92 lines
3.3 KiB
TOML
92 lines
3.3 KiB
TOML
id = "bug-triage"
|
|
name = "Bug Triage & Fix Plan"
|
|
description = "Analyse a bug report, reproduce the failure path, identify root cause, and produce a prioritised fix plan with test cases."
|
|
category = "engineering"
|
|
tags = ["bug", "debugging", "triage", "engineering"]
|
|
|
|
[i18n.zh]
|
|
name = "Bug 分析与修复计划"
|
|
description = "分析 Bug 报告，还原失败路径，定位根因，输出优先级排序的修复计划与测试用例。"
|
|
|
|
[[parameters]]
|
|
name = "bug_report"
|
|
description = "The bug report, error message, or stack trace"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "codebase_context"
|
|
description = "Relevant code snippets or architecture description"
|
|
param_type = "string"
|
|
required = false
|
|
default = ""
|
|
|
|
[[steps]]
|
|
name = "reproduce_path"
|
|
prompt_template = """
|
|
You are a senior engineer doing bug triage. Given the bug report below, reconstruct the exact failure path:
|
|
1. Preconditions that must be true
|
|
2. Step-by-step sequence that triggers the bug
|
|
3. What the system does vs. what it should do
|
|
4. Affected components and data flow
|
|
|
|
Bug report:
|
|
{{bug_report}}
|
|
|
|
Codebase context:
|
|
{{codebase_context}}
|
|
"""
|
|
|
|
[[steps]]
|
|
name = "root_cause"
|
|
prompt_template = """
|
|
You are a debugging expert. Based on the failure path analysis, identify the root cause:
|
|
1. Immediate cause (the direct code/logic fault)
|
|
2. Contributing factors (environment, race condition, assumption violation)
|
|
3. Why this was not caught earlier (missing test, wrong assumption)
|
|
4. Blast radius — what else could be affected
|
|
|
|
Failure path:
|
|
{{reproduce_path}}
|
|
"""
|
|
depends_on = ["reproduce_path"]
|
|
|
|
[[steps]]
|
|
name = "fix_plan"
|
|
prompt_template = """
|
|
You are a tech lead. Produce a concrete fix plan:
|
|
1. **Recommended fix** — specific code change with rationale
|
|
2. **Alternative approaches** — trade-offs of each
|
|
3. **Test cases to add** — unit, integration, regression
|
|
4. **Rollout recommendation** — hotfix vs. normal release, feature flag needed?
|
|
5. **Prevention** — process or tooling changes to prevent recurrence
|
|
|
|
Root cause analysis:
|
|
{{root_cause}}
|
|
"""
|
|
depends_on = ["root_cause"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "Bug 分流與修復計劃"
|
|
description = "分析 Bug 回報、還原失敗路徑、定位根因，輸出優先級排序的修復計劃與測試案例。"
|
|
|
|
[i18n.ja]
|
|
name = "バグトリアージと修正計画"
|
|
description = "バグレポートを解析し、失敗経路を再現し、根本原因を特定して優先度付きの修正計画とテストケースを出力。"
|
|
|
|
[i18n.ko]
|
|
name = "버그 분류 및 수정 계획"
|
|
description = "버그 리포트를 분석하고, 실패 경로를 재현하고, 근본 원인을 파악해 우선순위가 매겨진 수정 계획과 테스트 케이스를 생성."
|
|
|
|
[i18n.de]
|
|
name = "Bug-Triage & Fix-Plan"
|
|
description = "Bug-Report analysieren, Fehlerpfad reproduzieren, Root-Cause identifizieren und priorisierten Fix-Plan mit Testfällen erstellen."
|
|
|
|
[i18n.es]
|
|
name = "Triage de bugs y plan de corrección"
|
|
description = "Analiza un reporte de bug, reproduce el camino de fallo, identifica la causa raíz y produce un plan de corrección priorizado con casos de prueba."
|
|
|
|
[i18n.fr]
|
|
name = "Triage de bugs & plan de correction"
|
|
description = "Analyser un rapport de bug, reproduire le chemin d'échec, identifier la cause racine et produire un plan de correction priorisé avec cas de test."
|