Files
Evan 7881d327a5 refactor: migrate icon fields from emoji to lucide:<name> tokens (#63)
* 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.
2026-04-17 22:04:26 +09:00

109 lines
3.2 KiB
TOML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
id = "incident-postmortem"
name = "Incident Postmortem"
description = "Turn raw incident notes into a structured postmortem: timeline, root cause, impact assessment, and action items."
category = "engineering"
tags = ["incident", "postmortem", "devops", "reliability"]
[i18n.zh]
name = "故障复盘"
description = "将原始故障记录整理为结构化复盘报告:时间线、根因分析、影响评估和行动项。"
[[parameters]]
name = "incident_notes"
description = "Raw notes, chat logs, or timeline from the incident"
param_type = "string"
required = true
[[parameters]]
name = "service_name"
description = "Name of the affected service or system"
param_type = "string"
required = false
default = ""
[[steps]]
name = "timeline"
prompt_template = """
You are an SRE writing a postmortem. From the raw incident notes below, reconstruct a clean chronological timeline:
- Format: [HH:MM UTC] — event description
- Include: first alert, detection, escalation, mitigation steps, resolution
- Note who was involved at each stage
- Mark the start and end of user impact
Service: {{service_name}}
Raw notes:
{{incident_notes}}
"""
[[steps]]
name = "root_cause_analysis"
prompt_template = """
Perform a thorough root cause analysis using the 5-Whys method:
1. Immediate trigger
2. Five-whys chain down to the systemic root cause
3. Contributing factors (monitoring gaps, process failures, dependency issues)
4. Detection gap — why it took as long as it did to detect
Timeline:
{{timeline}}
"""
depends_on = ["timeline"]
[[steps]]
name = "postmortem_report"
prompt_template = """
Write a complete postmortem report with these sections:
## Summary
One paragraph: what happened, impact, duration, resolution.
## Impact
Quantified: users affected, error rate, revenue/SLA impact.
## Timeline
(Use the timeline above)
## Root Cause
(Use the RCA above)
## What Went Well
## What Went Wrong
## Action Items
Table: | Action | Owner | Priority | Due date |
Minimum 5 concrete, measurable actions.
## Lessons Learned
Timeline:
{{timeline}}
Root cause analysis:
{{root_cause_analysis}}
"""
depends_on = ["timeline", "root_cause_analysis"]
[i18n.zh-TW]
name = "事故復盤"
description = "將原始故障記錄整理為結構化復盤報告:時間線、根因分析、影響評估與行動項。"
[i18n.ja]
name = "インシデント ポストモーテム"
description = "生のインシデントメモを構造化されたポストモーテムに整理:タイムライン、根本原因、影響評価、アクションアイテム。"
[i18n.ko]
name = "장애 포스트모템"
description = "원시 장애 기록을 구조화된 포스트모템으로 정리: 타임라인, 근본 원인, 영향 평가, 액션 아이템."
[i18n.de]
name = "Incident-Postmortem"
description = "Rohe Vorfallsnotizen in ein strukturiertes Postmortem umwandeln: Timeline, Root Cause, Impact-Analyse und Action-Items."
[i18n.es]
name = "Postmortem de incidentes"
description = "Convierte notas de incidente en un postmortem estructurado: línea de tiempo, causa raíz, evaluación de impacto y acciones."
[i18n.fr]
name = "Post-mortem d’incident"
description = "Transformer des notes brutes d’incident en post-mortem structuré : chronologie, cause racine, évaluation d’impact et actions."