issue-implement

Automate GitHub issue lifecycle from triage to merge within the pycc repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of managing the software development lifecycle by autonomously handling the entire process from issue triage to final code merge.

Core Features & Use Cases

  • Autonomous Workflow: Manages the full cycle including staleness checks, planning, implementation, and deep code review.
  • Quality Assurance: Enforces strict CI monitoring and requires a clean diff review before merging.
  • Use Case: Use this skill to resolve a complex bug or feature request in the pycc repository without needing to manually coordinate the planning, coding, and review steps.

Quick Start

Invoke the issue-implement skill to resolve the GitHub issue numbered 42 in the current repository.

Frequently Asked Questions about issue-implement

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

FAQPage Schema
How do I automate GitHub issue resolution from triage to merge?

Autonomous GitHub issue resolution automates the full lifecycle including staleness checks, planning, implementation, deep code review, and final merging.

Can I use autonomous code generation for complex bug fixes in my repository?

Yes, autonomous code generation handles complex bug fixes and feature requests by managing planning, implementation, and validation without manual coordination steps.

What's the best way to enforce CI gates during autonomous software development?

Enforce CI gates during autonomous software development by requiring strict CI monitoring and a clean diff review before merging any code changes.

Does issue tracking automation work with documented development standards?

Yes, issue tracking automation requires strict adherence to the repository's internal CI gates and documented development standards throughout the implementation lifecycle.

Why does autonomous code review require a clean diff before merging?

Autonomous code review requires a clean diff before merging to ensure quality assurance and prevent unreviewed or invalid code changes from entering the repository.