beeui-implement-issue

Implements approved BeeUI issues in a verified target worktree with full verification evidence.

Updated May 30, 2026
One-click install
npx skills add https://github.com/beesyst/beeui --skill beeui-implement-issue-beesyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beeui-implement-issue
Source: https://github.com/beesyst/beeui/tree/main/.agents/skills/beeui-implement-issue
Command: npx skills add https://github.com/beesyst/beeui --skill beeui-implement-issue-beesyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined, gated workflow for implementing an approved BeeUI issue so changes stay within approved scope, land in the exact target worktree and branch, and ship with complete test and verification evidence instead of ad-hoc edits. ## Core Features & Use Cases - Target verification gates: Confirms working directory, branch, and git status before any edit, and stops on mismatches or unrelated pre-existing changes. - Change-level classification: Classifies work as low-risk, runtime-risk, or security-sensitive using SDLC and security docs, then derives proportional checks. - Evidence-based reporting: Produces a consolidated implementation report covering acceptance criteria, executed commands with exit codes, security review, and dependency/version status. - Use Case: After a BeeUI issue is approved and a feature branch is prepared, run this workflow to implement exactly the approved scope, run the required test suite via uv run, and return a structured report ready for review. ## Quick Start Implement the approved BeeUI issue in the specified target worktree on the expected branch and return the full implementation and verification report.

Frequently Asked Questions about beeui-implement-issue

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

FAQPage Schema
How do I implement an approved BeeUI issue safely?

Provide the exact target worktree, expected branch, base branch, and the approved issue contract. The workflow verifies the environment first, implements the smallest complete solution within approved scope, runs required checks, and returns a structured evidence report.

What inputs are required before running this implementation workflow?

You need the project, exact target worktree, expected branch, base branch, and the approved issue or normalized task contract. Optional inputs include the issue source, planning constraints, and explicitly supplied related-repository contracts.

Does this workflow commit, push, or create pull requests?

No. The workflow explicitly forbids committing, pushing, creating or updating PRs, and merging. It only modifies the target worktree, runs local checks, and returns an implementation report with a recommended Conventional Commit message.

What happens if the worktree or branch does not match the request?

The workflow stops immediately when the path differs from the requested target, the branch differs from the expected branch, or unrelated changes prevent safe attribution. It never silently switches branches or substitutes another worktree.

How are tests and verification checks determined for a change?

Checks are derived from the approved issue, the actual change level (low-risk, runtime-risk, or security-sensitive), and the SDLC and security docs. Every executed command is recorded with exit code, pass/fail/skip counts, and warnings.

Can the workflow change dependencies or the project version?

No, unless the approved issue explicitly requires it. Dependency declarations and the project version stay unchanged, and the report ends with a version status statement confirming this.