p:forge

Name: p:forge
Availability: InStock
Author: pontscho

Route build, test, and clean commands through forge_call when project-forge.yaml exists.

1|Updated Jan 7, 2026

Search Tags:#automation #build #yaml #pipelines #forge_call #project-forge

Ready to run

npx skills add https://github.com/pontscho/prompt-heaven --skill p-forge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: p:forge
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Aforge
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that, whenever project-forge.yaml exists at the project root, all build, test, and clean operations are executed exclusively through the forge_call MCP tool. It replaces ad-hoc Bash invocations with a controlled orchestration layer, enforcing consistent pipelines and safer execution.

Core Features & Use Cases

Author and edit project-forge.yaml (a minimal YAML subset) to define build, test, and clean pipelines.
Invoke forge_call for builds, tests, and cleans (mcp__mcp-forge__forge_call) and avoid Bash.
Use environment overrides, filters, and per-target options to control execution.

Quick Start

Create or edit project-forge.yaml and run forge_call to execute a build pipeline.

Frequently Asked Questions about p:forge

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

FAQPage Schema

How do I automate build and test pipelines using a YAML configuration file?▼

Build orchestration through forge_call requires a project-forge.yaml file at the project root to define pipelines, automatically replacing ad-hoc Bash invocations with a controlled execution layer for consistent builds.

How do I route build and test commands through a controlled orchestration layer instead of Bash?▼

When project-forge.yaml exists at the project root, all build, test, and clean operations are automatically routed through the forge_call MCP tool instead of Bash to enforce consistent pipelines and safer execution.

Does forge_call support environment overrides and validation for build pipelines?▼

Yes, forge_call supports environment overrides, filters, per-target options, and validation operations to control pipeline execution and guide usage defined in your project-forge.yaml file.

What is the best way to ensure consistent build execution across a software project?▼

Defining a minimal YAML subset in project-forge.yaml enforces a controlled orchestration layer by routing all build, test, and clean commands through forge_call, replacing ad-hoc Bash invocations with consistent pipelines.

Do I need a specific file to activate automated build and test orchestration?▼

Yes, a project-forge.yaml file must exist at the project root to activate build and test orchestration, ensuring every build, test, and clean command routes through forge_call instead of Bash.

Why should I replace ad-hoc Bash invocations with a YAML-driven orchestration layer?▼

Replacing ad-hoc Bash invocations with a YAML-driven forge_call orchestration layer enforces consistent pipelines and safer execution by centralizing control over all build, test, and clean operations.