one-shotting

Automate ticket-to-merge workflows with branch creation, tests, code, and PRs.

Updated Nov 23, 2022
One-click install
npx skills add https://github.com/tjmgregory/.dotfiles --skill one-shotting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-shotting
Source: https://github.com/tjmgregory/.dotfiles/tree/main/agents/skills/one-shotting
Command: npx skills add https://github.com/tjmgregory/.dotfiles --skill one-shotting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire process of taking a ticket from inception to a merged pull request, handling planning, coding, testing, and review loops.

Core Features & Use Cases

  • End-to-end ticket implementation: Manages the full software development lifecycle for a given ticket.
  • Autonomous workflow: Executes planning, TDD, PR creation, automated review, and merging without constant user intervention.
  • Use Case: When you have a new feature request or bug ticket (e.g., "Implement user profile editing"), you can invoke this skill with the ticket ID, and it will deliver the tested, reviewed, and merged code.

Quick Start

Use the one-shotting skill to implement ticket ID 'PROJ-123'.

Frequently Asked Questions about one-shotting

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

FAQPage Schema
How do I automate the ticket-to-merge workflow for continuous integration?

Automating the ticket-to-merge workflow involves using a skill that autonomously creates branches, writes tests, implements code, and manages PR reviews. It executes planning, TDD, and merging without constant user intervention.

Can I autonomously implement code and create pull requests from a ticket ID?

Yes, you can autonomously implement code and create pull requests by invoking the skill with a ticket ID. It handles planning, TDD, automated PR review, and merging to deliver tested code.

Does autonomous code review and fixing require integration with other development workflow skills?

Yes, autonomous code review and fixing requires integration with skills for ticket management, spec cascading, PR review, and merging. These integrations ensure adherence to repository agent file rules and TDD principles.

What is the best way to manage end-to-end ticket implementation using TDD principles?

The best way to manage end-to-end ticket implementation using TDD principles is through an autonomous workflow that writes tests, implements code, and manages sub-agent review loops. This ensures tested, reviewed, and merged code for feature requests.

When do I need an autonomous development workflow for ticket management?

You need an autonomous development workflow for ticket management when you have a new feature request or bug ticket and want to automate the process from inception to merged pull request. It handles planning, coding, testing, and review loops.

Are there limitations when using autonomous sub-agent reviews for code implementation?

A limitation of autonomous sub-agent reviews for code implementation is the strict dependency on separate skills for ticket management, spec cascading, PR review, and merging. Without these integrated components, the autonomous workflow cannot complete.