forge-pipeline-library

Scan, fingerprint, process, and bundle game assets into .forgepak archives.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill forge-pipeline-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-pipeline-library
Source: https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317/tree/main/.claude/skills/forge-pipeline-library
Command: npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill forge-pipeline-library

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use the forge-gpu asset pipeline library — a pip-installable Python package at the repo root for scanning, fingerprinting, processing, and bundling game assets with a plugin architecture. Use when working with pipeline code, writing plugins, processing textures/meshes/animations, bundling assets, or extending the pipeline CLI.

Core Features & Use Cases

  • Scans raw assets and computes content hashes to enable incremental builds.
  • Processes textures, meshes, and animations into GPU-ready formats using a plugin system.
  • Bundles processed assets into portable archives and exposes a CLI for end-to-end workflows.

Quick Start

Install in editable mode from the repo root and start using forge-pipeline to scan, process, and bundle assets.

Frequently Asked Questions about forge-pipeline-library

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

FAQPage Schema
How do I automate asset scanning and bundling for game assets?

Automating asset scanning and bundling for game assets is handled through a plugin-based Python pipeline that scans raw assets, computes content hashes, processes them into GPU-ready formats, and packages them into .forgepak bundles for deployment.

How does asset fingerprinting work for incremental builds?

Asset fingerprinting for incremental builds works by scanning raw assets and computing content hashes, enabling the pipeline to identify changed files and avoid reprocessing unchanged assets during subsequent bundling operations.

Can I extend the asset pipeline CLI with custom plugins for texture and mesh processing?

Extending the asset pipeline CLI with custom plugins for texture and mesh processing is fully supported through its plugin architecture, allowing you to write new plugins that process textures, meshes, and animations into GPU-ready formats.

What's the best way to package processed game assets into portable archives?

The best way to package processed game assets into portable archives is using the pipeline's bundling feature, which creates .forgepak bundles containing processed assets along with metadata sidecars for deployment.

Does the asset pipeline support dependency-aware bundling with per-plugin settings?

Dependency-aware bundling with per-plugin settings is supported by the asset pipeline, which parses configuration to manage plugin discovery, dependency resolution, and metadata sidecar generation during the packaging process.

Why do I need a plugin architecture for processing game assets?

A plugin architecture for processing game assets is needed to modularize the transformation of textures, meshes, and animations into GPU-ready formats, allowing independent configuration and extensible processing workflows.