skills.rest
moongci38-oss
moongci38-ossCOMMUNITY
Explore all skills by this author →
GitHub

forge-router

Detect .specify/ directories and start Forge Dev pipelines for code changes.

Updated Aug 23, 2026
Search Tags:#automation#hotfix#session-resume#signal-detection#dev-pipeline#forge-router
One-click install
npx skills add https://github.com/moongci38-oss/forge --skill forge-router
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-router
Source: https://github.com/moongci38-oss/forge/tree/main/.claude/skills/forge-router
Command: npx skills add https://github.com/moongci38-oss/forge --skill forge-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates starting Forge Dev pipelines when a project contains a .specify/ directory, ensuring code-change requests trigger an automatic orchestration and reduce manual overhead.

Core Features & Use Cases

  • Automatic detection of .specify/ directories to trigger Forge Dev routing for eligible projects.
  • Distinguishes Hotfix vs Standard changes and routes accordingly to Forge Dev's implicit entry.
  • Detects existing Forge Dev sessions and offers resume or new session initiation when needed.

Quick Start

Ensure your project includes a .specify/ directory to enable automatic Forge Dev routing for code change requests.

Frequently Asked Questions about forge-router

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

FAQPage Schema
How do I automate Forge Dev pipeline routing for code changes?▼

To automate Forge Dev pipeline routing, your project must include a .specify/ directory. This directory acts as a trigger, automatically routing code change requests such as feature implementation, refactoring, and bug fixes to the pipeline.

How does Forge Dev handle hotfix versus standard code changes?▼

Forge Dev classifies hotfix versus standard code changes by detecting the .specify/ directory. It then routes the work type accordingly to the pipeline's implicit entry point to ensure proper orchestration.

Can I resume an existing Forge Dev session after a code change request?▼

Yes, you can resume an existing Forge Dev session. The automation mechanism detects prior sessions and offers the option to resume the existing session or initiate a new one when processing code change requests.

Do I need a .specify/ directory to trigger Forge Dev automation?▼

Yes, a .specify/ directory is required to trigger Forge Dev automation. Its presence is the specific signal used to enable automatic routing for eligible development projects handling code changes.

What types of development tasks can be routed through Forge Dev automation?▼

Forge Dev automation routes development tasks including feature implementation, bug fixes, refactoring, API development, and UI work. This routing requires the project to contain a .specify/ directory.

Related Skills

Explore More Software Engineering Skills→
moongci38-ossmoongci38-oss

agent-drift-auditor

Detect agent drift and audit harness integrity in the Forge Dev pipeline.

Community
Advanced
ormastesormastes
1

dev

Run the 8-phase SStack pipeline for development tasks.

Community
Intermediate
lennystepn-huelennystepn-hue

frontend/public/skill

Manage project context and detect environment drift for Claude Code sessions.

Community
Advanced
allenhutchisonallenhutchison
515

review-queue

Triages blocked auto-dev pipeline items and executes human decisions.

Community
Intermediate