beaver-engine

Manage GitHub issue lifecycles with Project V2 fields and Issue Types.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/primatrix/skills --skill beaver-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beaver-engine
Source: https://github.com/primatrix/skills/tree/main/plugins/beaver/skills/beaver-engine
Command: npx skills add https://github.com/primatrix/skills --skill beaver-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The beaver-engine Skill Unit offers an internal engine to manage GitHub issue workflows efficiently, eliminating manual and repetitive tasks while ensuring project progression and quality.

Core Features & Use Cases

  • Issue Lifecycle Management: Manage the lifecycle of GitHub issues using Project V2 fields and native GitHub Issue Types.
  • Automated Transitions: Automate issue status transitions based on defined rules and conditions.
  • Guardrails: Implement guardrails to ensure quality and consistency in issue handling.
  • Use Case: Enhance your development workflow by automatically tracking and managing issues' progress through different states.

Quick Start

Set the status of an issue using the command 'beaver-status issue-number status-name'

Frequently Asked Questions about beaver-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue lifecycle management with Project V2 fields?

Automate GitHub issue lifecycle management by using scripts to update Project V2 fields and native Issue Types. This engine enforces guardrails and handles status transitions automatically, eliminating repetitive manual tracking tasks within a repository.

How do I enforce guardrails for issue status transitions in GitHub Actions?

Enforce guardrails for issue status transitions by applying defined rules and conditions through automated scripts. The engine validates state changes against native GitHub Issue Types before committing updates, ensuring consistency and quality in issue handling workflows.

Can I use GitHub Issue Types to track issue progress automatically?

Track issue progress automatically by mapping native GitHub Issue Types to Project V2 fields. The engine reads these field operations to determine current states and triggers transitions, streamlining the handling of issues through different lifecycle stages.

What's the best way to update an issue status using beaver-engine?

Update an issue status by running the 'beaver-status' command with the specific issue-number and target status-name. This script interfaces with the GitHub API via beaver-lib.sh to execute the transition and sync Project V2 fields.

Do I need the GitHub API to manage issue workflows with this engine?

The GitHub API is required to manage issue workflows with this engine. The scripts rely on specific field operations executed through beaver-lib.sh to communicate with GitHub, enabling automated transitions and Project V2 field updates.