beesdk-implement-issue

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing approved issues in a shared SDK repository often leads to scope creep, wrong-branch edits, unverified changes, and incomplete reporting. This Skill enforces a disciplined workflow that implements exactly one approved BeeSDK issue in the correct worktree and returns complete implementation and verification evidence. ## Core Features & Use Cases - Target Safety Gate: Verifies working directory, branch, git status, and pre-existing changes before touching any file, stopping when the worktree does not match the requested target. - Change Classification and Checks: Classifies work as low-risk, runtime-risk, or security-sensitive and derives required checks (pytest, uv build, smoke tests, SAST/SCA) from docs/SDLC.md and docs/SECURITY.md. - Structured Implementation Report: Produces a 17-section report covering files read, acceptance criteria coverage, test commands with exit codes, security review, and version status. - Use Case: A maintainer approves a BeeSDK issue to add a new public contract. The Skill reads AGENTS.md and the roadmap, implements the minimal KISS change in the prepared worktree, runs proportional tests, and returns evidence without committing or changing the package version. ## Quick Start Implement the approved BeeSDK issue in the prepared target worktree on its expected branch and return the full implementation and verification report.

Frequently Asked Questions about beesdk-implement-issue

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

FAQPage Schema
How do I implement an approved GitHub issue in a specific git worktree?

Verify the current working directory, branch, and git status match the requested target before editing. Then read the approved issue and repository contracts, make the smallest complete change, run the required checks, and report exact commands and exit codes.

What checks should run for a low-risk versus security-sensitive code change?

Derive required checks from the repository's SDLC and security documentation based on the classified change level. Low-risk changes need targeted tests, while security-sensitive changes add SAST, SCA, and deeper verification such as public API and package contents checks.

Can this workflow commit, push, or create a pull request?

No. The workflow explicitly forbids committing, pushing, creating PRs, or merging. It only implements the change in the target worktree and returns evidence, ending with a recommended Conventional Commit message for a human to apply.

What happens if the worktree or branch does not match the requested target?

The workflow stops immediately when the path or branch differs from the requested target, or when unrelated pre-existing changes make safe attribution impossible. It never silently switches branches or substitutes another worktree.

When should the package version in pyproject.toml be changed?

Only when the approved issue is explicitly release-related. Ordinary feature, fix, docs, and chore work keeps pyproject.toml version unchanged, and the report ends with a version not changed statement.