skills.rest
marcuskrogh
marcuskroghCOMMUNITY
Explore all skills by this author →
GitHub

iterate

Create tasks, branches, and pull requests for post-ship fixes linked to prior work.

1|Updated Jul 1, 2026
Search Tags:#workflow#maintenance#iteration#pull-request#task-tracking#bug-fix
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill iterate-marcuskrogh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iterate
Source: https://github.com/marcuskrogh/skills/tree/main/skills/iterate
Command: npx skills add https://github.com/marcuskrogh/skills --skill iterate-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the friction of managing follow-up fixes for already merged work by automating the creation of new branches, tasks, and PRs while maintaining clear lineage to the original implementation.

Core Features & Use Cases

  • Automated Iteration Loop: Creates a new task, branch, and PR specifically for post-ship fixes, ensuring the original merged work remains intact.
  • Context Preservation: Automatically links new iteration tasks to the original task, plan, and PR for full traceability.
  • Use Case: If a feature is merged but a minor bug is discovered in production, use this skill to quickly spin up a fix-forward cycle that keeps your project tracker and documentation perfectly synced.

Quick Start

Invoke the iterate skill by providing the original task key and a brief description of the issue that needs to be addressed.

Frequently Asked Questions about iterate

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

FAQPage Schema
How do I automate post-ship bug fixes for merged pull requests?▼

Automating post-ship bug fixes involves creating new tasks, branches, and PRs linked to prior work to maintain traceability. This ensures the original merged feature remains intact while follow-up adjustments are tracked separately.

What is the best workflow for tracking iterative changes after a feature ship?▼

The best workflow for tracking iterative changes links new iteration tasks to the original task, plan, and PR. This preserves full context and lineage, standardizing documentation for software maintenance without losing historical data.

How do I spin up a fix-forward cycle for a production bug?▼

Spinning up a fix-forward cycle requires providing the original task key and a brief description of the issue. This automatically generates a new branch and pull request to address the bug while keeping your project tracker synchronized.

Can I maintain branch isolation when applying follow-up adjustments to merged work?▼

Yes, maintaining branch isolation during follow-up adjustments is achieved by creating a dedicated new branch for the fix. This prevents direct modifications to the merged work, ensuring standardized documentation and safe iterative changes.

Do I need to manually link new pull requests to original project plans?▼

No, you do not need to manually link new pull requests to original plans. Context preservation automatically links new iteration tasks to the original task, plan, and PR for full traceability across the maintenance workflow.

Related Skills

Explore More Software Engineering Skills→
HillBombCreationsHillBombCreations

cmd-document

Generate bug fix documentation and pull request descriptions from issue artifacts.

Official
Intermediate
edmundmilleredmundmiller
78

Understanding Jujutsu Merges and Conflicts

Explain Jujutsu merge semantics, empty merge commits, and conflict resolution.

Community
Advanced
nbarthelemynbarthelemy

autonomous-loop

Manage autonomous iterative development loops with checkpointing, cost tracking, and safety limits.

Community
Advanced
791994545791994545
4

ralph-loop

Automate TDD loop setup with verification commands and task tracking.

Community
Advanced