fix

Apply review fixes across sprint branches and worktrees.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill fix-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/fix
Command: npx skills add https://github.com/tjisousa/gensem --skill fix-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of applying fixes from review findings in the current sprint.

Core Features & Use Cases

  • Automates management of review findings and sprint fixes.
  • Supports git-based patch application and merge strategies across branches and worktrees.
  • Use Case: A developer applies fixes for findings in the current sprint and merges back to the feature branch.

Quick Start

Execute the fix workflow to address all findings in the current sprint.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I automate applying fixes from code review findings to sprint branches?

Automating fixes from review findings involves applying git-backed patches across sprint branches and worktrees. This approach enforces sprint status and backlog tracking guardrails while supporting multiple merge strategies and configuration awareness.

What is the best way to merge code review fixes back to a feature branch?

Merging code review fixes back to a feature branch is handled through configurable merge strategies within the fix workflow. The process targets sprint-based software projects and applies patches across git branches and worktrees.

Does git worktree patching support multiple merge strategies for sprint fixes?

Git worktree patching supports multiple merge strategies for sprint fixes. The skill applies review findings across branches and worktrees while enforcing sprint status guardrails and maintaining backlog tracking.

How do I apply review findings automatically in a sprint-based development workflow?

Applying review findings automatically in a sprint-based workflow requires executing the fix workflow. It addresses all findings in the current sprint by leveraging git-based patch application and backlog tracking guardrails.

Do I need active sprint status and backlog tracking to automate git patching for review findings?

Active sprint status and backlog tracking are required guardrails to automate git patching for review findings. The skill enforces these constraints to ensure fixes are applied correctly within the current sprint context.