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

dev

Load when implementing an issue or applying review fixes as a dev agent.

vanillagreencom · 已有 AI 审核记录

安装与使用

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

npx skills add vanillagreencom/kendex --skill dev

技能说明


name: dev description: "Load when implementing an issue or applying review fixes as a dev agent." summary: "Dev-agent workflows for implementing an issue and applying review fixes, invoked by orch or specialist agents." license: MIT user-invocable: true dependencies: required: [orch, github, decider, code-quality] optional: [linear] metadata: author: vanillagreen source: kendex repository: "https://github.com/vanillagreencom/kendex" bugs: "https://github.com/vanillagreencom/kendex/issues" version: "2.0.0" tags: [automation]

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

Dev Workflows

orch is the caller and runtime: it owns delegation format, round acceptance, and every shell-shape rule.

WorkflowPurpose
workflows/dev-implement.mdImplementation: activate → plan → implement → validate → commit → QA labels → summary → artifact → return (§ 1-11)
workflows/dev-fix.mdReview fixes: evaluate → apply or skip → validate → commit → artifact → return

Review and QA-review belong to the reviewer skill: ../reviewer/workflows/review.md, ../reviewer/workflows/qa-review.md. Command shapes are orch's ../orch/SKILL.md § Harness-Safe Shell; literal format tags and round mechanics are its ../orch/references/skill-rules.md § Format Tags Are Literal and § Round Closure.

Engineering Rules

  • Scope is the issue's Done-when. A behavioral surface that does not trace to it stays out of this change, and a committed render of a source file you changed traces to whatever its source traces to. Two exceptions:
    • the mechanical enablers of landing it ride without tracing to it: locks, changelog, baselines, dismissal renewals, that list and nothing else, never code that runs at runtime;
    • a defect the change introduces or arms is in scope by definition, unless Step 0 of ../orch/references/finding-disposition.md excludes it.
  • Every behavior change ships with a test that runs against the script or program enforcing it, at the smallest surface that fails. A workflow sentence ships no test. A test that pins prose, drives a second implementation, or stubs the function under test does not count as a test.
  • A review finding adds a case only when it names a behaviour no existing case reaches. Otherwise it tightens the existing case's assertion, and the item reasoning names that case.
  • A second fix round on the same function's guard is recurrence: redesign the rule under test so the class is unrepresentable, and fold the family of cases into one table.
  • A test whose premise died is deleted whole in the commit that kills the premise, and the PR body names the deletion.
  • Test shape (one control per surface, tables for shaped input, one file per surface) is code-quality § Tests.
  • A refusal, a validator, a lock, a retry, or a test exists only for an input a real producer emits, this project's code or anything it calls or serves; name that producer beside it, or do not write it.
  • When a change deletes a call, apply code-quality § Cleanup to its callee. Its deletion maps to the call removal's Done-when item; no internal caller is not proof that a supported external API is unused.
  • A field, setting, or view member added by the change has a real producer and consumer. A named and documented external producer or consumer is valid when the change adds its in-repository counterpart; otherwise, add both sides in the change.
  • No migration or compat code for this project's own formats, its manifest, settings, lock and cache shapes, never another tool's on-disk state, which an adapter may have to keep recognising: write no reader for an artifact an older version of this project wrote, and decline a finding that asks you to carry one forward. A layout, schema or cache change is one changelog line and a fresh install.
  • Before adding a function, parser, stub or loop, grep the repo for the verb it performs; before stating a rule, grep for the rule.
    • A second copy of that verb, in any language, is a twin and never delegation, and so is a second statement of a rule another file owns, in prose, config or a table.
    • Call or cite the one that exists, or escalate in your return. An issue that orders a twin is escalated, not implemented.
  • Docs move with the code they describe; the docs-writing skill states the rule and the doc-drift-check hook shows the user docs that may need an update.
  • Once a pushed head has been reviewed, later rounds add commits and never amend; before any review has run on a head, the kendex-issues fix cycle may amend only to refresh a required check that cannot be rerun.
  • A push that prints rebase-map: lines has rewritten the shas the PR's Fixed in <sha> replies name: before holding, re-reply each such thread with the new sha, or post the map as one PR comment naming old and new per line; a sha the map reports as dropped gets a reply that the fix commit no longer exists on the branch.

Code standards are ../code-quality/SKILL.md: correctness, comments, over-engineering, cleanup.

Round Contract

Execute workflow sections in order; a "Skip if" condition is the workflow's decision, never your own scope assessment. Never push and never open a PR. The orchestrator does that after review passes. A finding on a mechanism this diff introduces or arms is a fix whatever the round, unless Step 0 of the disposition flow excludes it; a Declined: there takes one of the reason forms [`../orch/references/finding-

阅读完整来源 ↗