twig-changes

Author, validate, apply, and recover Twig change proposals for Azure DevOps work items.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/PolyphonyRequiem/twig --skill twig-changes-polyphonyrequiem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twig-changes
Source: https://github.com/PolyphonyRequiem/twig/tree/main/.github/skills/twig-changes
Command: npx skills add https://github.com/PolyphonyRequiem/twig --skill twig-changes-polyphonyrequiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applying multi-item changes to Azure DevOps work items through Twig requires careful validation, authorization, and recovery handling; this Skill provides the procedure for authoring, reviewing, applying, and recovering Twig change proposals without guessing or unsafe retries. ## Core Features & Use Cases - Proposal Authoring and Validation: Create proposals with the native schema, run twig proposal validate and twig proposal preview, and inspect digests, operations, preconditions, and blockers before applying. - Controlled Apply and Verification: Apply only the exact reviewed digest with the required authorizer, then refresh-read affected items to confirm what actually landed, reporting per-item outcomes. - Safe Recovery: Read the native journal before retrying interrupted applies, reconcile unknown outcomes against authoritative reads, and author fresh proposals when native recovery requires it. - Use Case: An agent needs to transition and update several ADO work items in one board change; it seeds identities, previews the proposal, obtains approval, applies the digest, and reports verified per-item results. ## Quick Start Ask the agent to prepare and apply a Twig change proposal for the target work items, loading the twig-cli skill first and following the validate, preview, review, apply, and verify procedure.

Frequently Asked Questions about twig-changes

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

FAQPage Schema
How do I apply a Twig change proposal to Azure DevOps work items?

Author the proposal in the workspace, run twig proposal validate and preview, review the exact digest under the user's authority, then apply it with twig proposal apply using the required authorizer. Afterwards, read twig proposal status and refresh-read the affected items to verify results.

How do I recover an interrupted twig proposal apply?

Read the native Twig journal before retrying, since it records actual operation states and recovery rules. Reconcile unknown outcomes against authoritative reads, preserve the old proposal as evidence, and author a fresh proposal for any remaining safe change.

Does twig proposal preview mutate Azure DevOps work items?

No, preview is a local journal write, not an ADO mutation. Its canApply result is not proof that remote revisions or process gates still hold at execution time, so verification after apply is still required.

Is a multi-item Twig proposal apply atomic?

No, a multi-item apply is not one atomic transaction. An earlier successful operation may remain committed after a later failure, so outcomes must be reported per item as successes, failures, unknown, or untouched.

When should I use twig proposal seed?

Use twig proposal seed for staged identities and fingerprints when authoring proposals. Do not predict published IDs or reuse transient aliases as durable identities, and never repeat seed creation just because the outer session lost its response.