implement

Name: implement
Availability: InStock
Author: usk6666

Automate software development from Linear issues to pull request creation.

11|1|Updated May 15, 2026

Search Tags:#automation #git #development workflow #pull request #github #coding #linear

Ready to run

npx skills add https://github.com/usk6666/yorishiro-proxy --skill implement-usk6666

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/usk6666/yorishiro-proxy/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/usk6666/yorishiro-proxy --skill implement-usk6666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire software development workflow from issue tracking to pull request creation, streamlining the development process and reducing manual overhead.

Core Features & Use Cases

End-to-End Workflow: Manages branch creation, coding, testing, committing, and PR generation based on Linear issues.
Automated Branching: Generates feature, fix, or chore branches with descriptive names.
Conventional Commits & PRs: Enforces commit message and PR formatting standards.
Automated Testing & Linting: Integrates gofmt, make lint, make build, and make test for code quality assurance.
Use Case: A developer can provide a Linear Issue ID, and the Skill will handle creating the branch, writing the code, running tests, committing the changes, and opening a pull request for review.

Quick Start

Use the implement skill to create a new feature branch and implement the changes for issue USK-12.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I automate the development workflow from a Linear issue to a GitHub pull request?▼

You can automate the workflow from a Linear issue to a GitHub pull request by providing a Linear Issue ID to trigger automated branch generation, code implementation, testing, and PR submission. The process integrates Linear, Git, and GitHub CLI for seamless end-to-end automation.

What is the end-to-end software development lifecycle automation process for issue tracking and pull requests?▼

End-to-end development lifecycle automation manages branch creation, code implementation, automated testing, conventional commits, and pull request generation. It bridges issue tracking in Linear with Git version control and GitHub PR submission to reduce manual overhead.

Can I enforce conventional commits and automated testing when creating a pull request from a Linear issue?▼

Yes, you can enforce conventional commits and automated testing when creating a pull request from a Linear issue. The automation runs gofmt, make lint, make build, and make test to assure code quality before submitting the PR.

Do I need the GitHub CLI and Git installed to automate branch generation and PR creation from Linear issues?▼

Yes, you need Git and the GitHub CLI installed to automate branch generation and PR creation from Linear issues. The workflow relies on these tools alongside Linear integration to manage version control and submit pull requests with automated status updates.

What's the best way to generate feature, fix, or chore branches automatically from issue tracking IDs?▼

The best way to generate feature, fix, or chore branches automatically from issue tracking IDs is using an automation skill that reads the Linear issue and creates a descriptively named branch. This ensures consistent branching conventions before coding and testing begin.

Why does automated pull request creation fail when local linting or build checks do not pass?▼

Automated pull request creation fails when local linting or build checks do not pass because the workflow integrates gofmt, make lint, make build, and make test for code quality assurance. The PR submission is gated by these automated checks to prevent broken code from being reviewed.