skills.rest
RyderFreeman4Logos
RyderFreeman4LogosCOMMUNITY
Explore all skills by this author →
𝕏@wuzhige4pixelGitHub

dev-to-merge

Redirects legacy dev-to-merge alias calls to the dev2merge workflow via /dev2merge endpoint or CSA plan run patterns/dev2merge/workflow.toml.

12|1|Updated Feb 6, 2026
Search Tags:#workflow#devops#integration#routing#alias#dev2merge#alias-legacy
One-click install
npx skills add https://github.com/RyderFreeman4Logos/cli-sub-agent --skill dev-to-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-to-merge
Source: https://github.com/RyderFreeman4Logos/cli-sub-agent/tree/main/patterns/dev-to-merge/skills/dev-to-merge
Command: npx skills add https://github.com/RyderFreeman4Logos/cli-sub-agent --skill dev-to-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-to-Merge provides a backward-compatible alias that redirects to the canonical dev2merge workflow, ensuring legacy integrations continue to function without changes.

Core Features & Use Cases

  • Legacy alias routing to the dev2merge pipeline, preserving workflows for teams migrating to the new system.
  • Directed to the canonical weave workflow via /dev2merge or the csa plan run patterns/dev2merge/workflow.toml.
  • See dev2merge's SKILL.md for the full pipeline documentation and behavior.

Quick Start

Invoke the legacy dev-to-merge alias to route execution to the dev2merge workflow.

Frequently Asked Questions about dev-to-merge

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

FAQPage Schema
How do I maintain legacy dev-to-merge aliases during a workflow migration?▼

To maintain legacy dev-to-merge aliases during a workflow migration, you can use an alias Skill that automatically redirects execution to the canonical dev2merge pipeline without changing your existing scripts or configurations.

What does the dev-to-merge alias route to in automation scripts?▼

The dev-to-merge alias routes automation scripts to the canonical dev2merge weave workflow via the /dev2merge endpoint or the csa plan run patterns/dev2merge/workflow.toml command pattern.

Can I use the legacy dev-to-merge alias for project onboarding with the new system?▼

Yes, you can use the legacy dev-to-merge alias for project onboarding. It provides backward compatibility by redirecting your onboarding calls directly to the dev2merge workflow, ensuring legacy integrations function without requiring code changes.

Do I need to update my CLI workflows if I use the dev-to-merge alias?▼

No, you do not need to update your CLI workflows if you use the dev-to-merge alias. It serves as a backward-compatible routing layer that ensures your existing CLI integrations continue functioning while directing execution to the dev2merge workflow.

Related Skills

Explore More Software Engineering Skills→
Mr-Fang-VLSIMr-Fang-VLSI
8

eda-chief

Map legacy eda-chief calls to current agent policies and eda-loop execution.

Community
Intermediate
RyderFreeman4LogosRyderFreeman4Logos
12

dev2merge

Automate feature-branch development from planning through PR merge with CSA tooling.

Community
Advanced
R3n3gade-aiR3n3gade-ai

skill-gen-4-enterprise-doc

Convert SOPs and documents into installable JiuwenClaw skills with SKILL.md frontmatter.

Community
Advanced
citumcitum
31

styleauthor

Alias the style-evolve workflow for backward-compatible legacy references.

Official
Basic