.claude/skills/dev-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
标准开发流程规范。每当接到新的开发任务或 bug 修复任务时必须先调用本 skill,按流程执行:从 master 拉分支 → 确认需求或复现 bug → 检查/补充测试覆盖 → 改动 → 回归测试 → 用户验收 → 发布。
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/dev-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/dev-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/dev-workflowRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @xiaoshidebug/dev-workflowclawhub inspect @xiaoshidebug/dev-workflow --version 0.1.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:d1e77c880e42593fb647fd77257ab8c2f668067fb693a1308c574177139c6983skill-card.mdSKILL.mdInitial release of development workflow guidelines: - Introduces a standardized process for handling all new feature and bug fix tasks, requiring strict step-by-step execution. - Defines branch creation rules, including naming conventions and strict separation from main/master. - Specifies mandatory requirements validation and bug reproduction procedures before coding. - Enforces test coverage checks and outlines steps for projects lacking a test framework. - Details user acceptance and release requirements, emphasizing no merging or publishing before user approval.