implementation

Implement approved GitHub issues by creating branches, committing changes, and opening pull requests.

Updated Feb 2, 2025

Search Tags:#workflow #github #implementation #branching #pull-request #project-board

Ready to run

npx skills add https://github.com/forrestthewoods/anubis --skill implementation-forrestthewoods

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/forrestthewoods/anubis/tree/main/.claude/skills/implementation
Command: npx skills add https://github.com/forrestthewoods/anubis --skill implementation-forrestthewoods

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements GitHub issues that have approved implementation plans by guiding the workflow from plan review to branch creation, code changes, and PR submission, ensuring a repeatable, auditable process.

Core Features & Use Cases

Fetch issue details and the approved implementation plan from the project board
Validate prerequisites (status, plan completeness) before starting work
Create a feature branch following standard naming conventions and implement the requested changes
Commit changes with issue references and push for review
Open a PR and update the project board accordingly, enabling traceability
Adaptable to typical team workflows and cross-project integration

Quick Start

Fetch the issue and its approved implementation plan, create a branch, implement changes per the plan, and submit a PR.

Frequently Asked Questions about implementation

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

FAQPage Schema

How do I implement a GitHub issue from an approved plan?▼

To implement a GitHub issue, this Skill fetches the approved plan, validates prerequisites, creates a feature branch, executes step-by-step code changes, and submits a pull request while updating the project board for full traceability.

What's the best way to manage branching and pull requests across a project board?▼

Managing branching and pull requests across a project board is handled by enforcing standard naming conventions, validating issue status prerequisites, and automatically linking pull requests back to their originating issues.

How does the GitHub issue implementation workflow enforce prerequisites?▼

The GitHub issue implementation workflow enforces prerequisites by validating the current issue status and confirming the completeness of the approved implementation plan before allowing branch creation or code changes to proceed.

Can I use this workflow to create a feature branch and update the project board?▼

Yes, you can create a feature branch following standard naming conventions, commit changes with issue references, push for review, and open a pull request that updates the project board to maintain full traceability.

What happens if an issue lacks an approved implementation plan?▼

If an issue lacks an approved implementation plan, the prerequisite checks will fail and block the workflow, ensuring teams only implement GitHub issues with properly validated and structured plans.

Does this GitHub workflow integrate with existing team branching conventions?▼

Yes, this GitHub workflow integrates with existing team conventions by enforcing standard branch naming, linking commits to issues, and updating the project board to adapt to typical cross-project integration workflows.