beaver-engine

Installation
SKILL.md

Beaver Engine

Internal skill. Do not invoke directly. Other beaver skills reference these rules and command templates.

Single source of truth for an Issue's lifecycle metadata is GitHub Projects V2 #14 custom fields and the native GitHub Issue Type — not labels. All read/write operations on lifecycle metadata go through plugins/beaver/scripts/beaver-lib.sh (see §4 Field Operations). Native GitHub Issues APIs that fall outside the lifecycle-metadata surface (e.g., the sub-issues API used by G009, the labels API used for beaver/* flag labels in §4) are called directly with gh api since they do not correspond to Project V2 fields or Issue Type.

废弃说明 (Deprecation Notice)

Earlier revisions of this engine modeled lifecycle metadata as status/*, type/*, and size/* repository labels. Those label families are deprecated and replaced by Project V2 fields and native Issue Types per RFC-0013. The old labels are kept on primatrix/projects for historical Issues but are no longer read or written by any Beaver command. New code MUST go through beaver-lib.sh.

Mapping for reference (legacy label → new field semantics):

Related skills
Installs
1
First Seen
7 days ago