Skip to main content

openclaw-dev-workflow

Enforce a production-grade development workflow for OpenClaw coding work. Use when the request is broad or end-to-end, such as "build this feature", "fix this properly", "handle this coding task", "implement this across the codebase", or "help me ship this safely", especially when work spans multiple files and needs planning, verification, and clean closeout.

来源信息

仓库
LeoYeAI/openclaw-coding-skills
最近来源活动
2026年4月28日 07:28
检测到的 SKILL.md 语言
英语
星标
2
分支
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
4 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
openclaw-dev-workflow
description
Enforce a production-grade development workflow for OpenClaw coding work. Use when the request is broad or end-to-end, such as "build this feature", "fix this properly", "handle this coding task", "implement this across the codebase", or "help me ship this safely", especially when work spans multiple files and needs planning, verification, and clean closeout.
# OpenClaw Dev Workflow Use this skill to orchestrate coding work end to end inside an OpenClaw workspace. This is the default workflow layer. Pair it with narrower domain skills when a task needs frontend, security, performance, deployment, or framework-specific depth. ## Core Rules - Read the local workspace contract before major work. - Let local rules override generic habits. - Create or update `plan.md` for long tasks when required. - Prefer first-class OpenClaw tools over improvised shell-heavy flows. - Verify before claiming completion. - End with a clean git commit unless told not to. ## Workflow ### 1. Frame - Classify the task. - Determine risk and breadth. - Decide whether direct execution or a staged plan is appropriate. ### 2. Gather context - Read only the files needed for the current slice. - Search for existing patterns before inventing new ones. - Retrieve prior context when historical decisions matter. ### 3. Execute in slices - Pick the smallest meaningful increment. - Implement it. - Verify it. - Update the task plan. ### 4. Close out - Review the final diff. - Update any required docs. - Commit. - Report evidence and residual risk. ## Reference Files Read when needed: - `references/task-shapes.md` - `references/verification-matrix.md` - `references/git-closeout.md`
在 GitHub 查看