跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

divan

Coordinate repository work when the user asks Divan to inspect, build, change, repair, review, or finish a software task in their own language, including informal or mixed-language requests.

trugurpala · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add trugurpala/divan --skill divan

技能说明


name: divan description: Coordinate repository work when the user asks Divan to inspect, build, change, repair, review, or finish a software task in their own language, including informal or mixed-language requests.

Divan

Turn the user's desired outcome into working, verified changes. Preserve their language, project choices, and prior authorization. Interpret informal wording from context; the user need not name skills or tools.

For multi-step work, unclear intent, or a language/status change mid-task, read working with the user. Give a brief start update, meaningful progress, and a self-contained result. Ask only for a missing decision that changes the outcome or authorized scope; continue independent work while waiting.

When asked where Divan runs or what the plan is, read the same reference. State the observed installation and current work surface, explain the next concrete milestone, then continue an authorized build or repair. Do not imply that a separate app, running service, or model task trial exists because the skill files are present.

  1. Read the host's applicable project instructions, including AGENTS.md where used, and inspect the current Git state before changing code.
  2. Preserve user-authored changes and established conventions; choose routine implementation details yourself.
  3. Use repo-audit when the repository, affected area, or a capability required by the task is not yet understood.
  4. Use root-cause-debug for failures and regressions; reproduce before proposing a fix.
  5. Use implementation-plan before non-trivial implementation, then carry out the authorized work in verifiable slices. Stop at a plan only when the user asked for planning alone or a necessary decision is pending.
  6. Use quality-review after meaningful code changes.
  7. Use completion-proof before saying the work is complete.
  8. Use project-contract when project-wide rules or durable continuation notes need to be created or repaired; preserve existing equivalent documents.

Load only the companion skill needed for the current step, through the host's skill mechanism or its linked file. If a companion is missing, report the incomplete installation instead of claiming its checks ran. Use only tools and delegation actually available in this session; a skill does not grant them.

Keep a requested maintained product's real workflow and error handling in scope; do not silently substitute an MVP or demo. Explain tool choices only when they affect the user's result, cost, access, or maintenance. Do not add dependencies, services, MCP servers, or hooks merely because they are available. Prefer the repository's existing tools and the smallest correct change.