oneshot-with-remote-feedback

Executes a plan into code in one parcel, publishing every commit to a remote branch.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Xalior/agent-skills --skill oneshot-with-remote-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oneshot-with-remote-feedback
Source: https://github.com/Xalior/agent-skills/tree/main/oneshot-with-remote-feedback
Command: npx skills add https://github.com/Xalior/agent-skills --skill oneshot-with-remote-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill executes a plan into code in a single uninterrupted parcel, publishing every commit so the remote branch is the live monitoring channel during execution; the human reviews the finished result at the end.

Core Features & Use Cases

  • End-to-end plan execution: Run plan-defined phases in order with no mid-parcel reviews.
  • Live commit publishing: Every commit is pushed so a remote branch acts as a live monitoring channel.
  • End-of-parcel review: Manual Success Criteria are evaluated only at the end; wrap-up actions apply afterwards.
  • Preflight-driven autonomy: Eleven preflight steps configure the execution context and PR strategy.

Quick Start

Provide a plan path to start execution and let it run end-to-end, publishing every commit and leaving the final review for after completion.

Frequently Asked Questions about oneshot-with-remote-feedback

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

FAQPage Schema
How do I execute a code migration plan end-to-end without pausing for per-commit review?

End-to-end plan execution runs plan-defined phases in order with no mid-parcel reviews, publishing every commit to a remote branch so you can monitor progress live and review the finished result afterwards.

What's the best way to automate a bulk code refactor while tracking progress on a remote branch?

Automating a bulk code refactor uses a single uninterrupted parcel that pushes every commit live, turning the remote branch into a real-time monitoring channel and deferring manual evaluation to an end-of-parcel review.

Does this workflow require a predefined plan path before starting a codemod?

Yes, this workflow enforces a plan-driven approach requiring a plan path to start execution, running eleven preflight steps to configure the execution context and PR strategy before the codemod begins.

When should I not use a one-shot execution flow for code transformations?

You should not use a one-shot execution flow for code transformations when per-commit review is valuable, because this approach defers manual success criteria evaluation entirely to the end of the parcel.

Can I use this for a git-workflow migration with continuous remote monitoring?

Yes, you can use this for a git-workflow migration because it enforces strict commit and push discipline, publishing every transformation live to the remote branch for continuous monitoring during execution.

How do preflight steps prepare the environment for an end-to-end code mod?

Eleven preflight steps configure the execution context and PR strategy before an end-to-end code mod, ensuring the environment is fully set up for autonomous, uninterrupted plan execution with live commit publishing.