skills.rest
gaiastudio-ai
gaiastudio-aiOFFICIAL
Explore all skills by this author →
GitHub

gaia-change-request

Redirect legacy change requests to the gaia-add-feature handler.

2|Updated Apr 15, 2026
Search Tags:#automation#compatibility#legacy#redirect#change-request#gaia
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-change-request
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gaia-change-request
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-change-request
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-change-request

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resolve-config.sh, checkpoint.sh, lifecycle-event.sh, and includes scripts (resource) components.

What problem does it solve?

Thin backward-compatible redirect that forwards legacy change requests to the canonical gaia-add-feature handler, preserving automation and audit trails.

Core Features & Use Cases

  • Backward compatibility: Keeps legacy change-request invocations functioning by routing to gaia-add-feature.
  • Transparent deprecation: Displays a deprecation banner while forwarding to the new workflow.
  • Reliable delegation: Ensures user-supplied arguments are passed verbatim to gaia-add-feature and results are relayed.

Quick Start

Provide your change request text to gaia-change-request to forward to gaia-add-feature.

Frequently Asked Questions about gaia-change-request

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

FAQPage Schema
How do I redirect legacy change requests to the new GAIA handler?▼

To redirect legacy change requests, this Skill forwards invocations to the canonical gaia-add-feature handler. It preserves backward compatibility for automation trails and downstream workflows while emitting a deprecation banner.

What is the best way to maintain backward compatibility for deprecated automation trails?▼

Maintaining backward compatibility for automation trails is achieved by routing legacy entry points to the canonical handler. This transparent delegation relays user arguments verbatim and preserves audit trails without breaking existing workflows.

Does the GAIA redirect pass user arguments verbatim to the new workflow?▼

Yes, the GAIA redirect ensures user-supplied arguments are passed verbatim to gaia-add-feature. It reliably delegates the invocation and relays the output back to the caller while displaying a deprecation banner.

Why does my legacy change-request invocation show a deprecation banner?▼

A deprecation banner appears because the legacy change-request invocation is being transparently redirected. This informs users that the entry point is deprecated while successfully forwarding their request to the gaia-add-feature handler.

Can I use legacy change-request entry points with downstream automation workflows?▼

Yes, you can use legacy entry points with downstream automation workflows. The redirect preserves audit trails and ensures reliable delegation, keeping existing automation functional without requiring immediate migration.

Related Skills

Explore More Software Engineering Skills→
elasticdotventureselasticdotventures
14

direnv-pattern

Automate loading of per-project environment variables via direnv and dotenv with Rust validation.

Community
Advanced
gaiastudio-aigaiastudio-ai
2

gaia-problem-solving

Orchestrate plan-approve-execute workflows and generate structured problem-solving artifacts.

Official
Advanced
gaiastudio-aigaiastudio-ai
2

gaia-validate-prd

Redirect legacy PRD validation calls to the gaia-val-validate validator.

Official
Basic
nghiahsgsnghiahsgs
32

taw-add

Forward legacy taw-add invocations to the /taw command.

Community
Basic