Quentin McClellan

Public project · v0.2.0

Forge: developer platform CLI for standardized project scaffolding.

Forge is a Python CLI that creates standardized project lanes from schema-driven templates. It validates local prerequisites, packages and publishes templates to a Nexus artifact registry, and produces projects with consistent structure, documentation, and release workflows.

Review proof Templates Forge MCP View on GitHub

Problem

Project scaffolding without discipline creates scaffolding without standards.

Starting a new service or pipeline is often the moment structure breaks down: inconsistent layouts, missing docs, undeclared dependencies, and no repeatable path from creation to release. Forge was built to replace ad-hoc project setup with a governed, template-driven workflow that produces consistent structure from the first commit.

Commands

Three commands cover creation, validation, and inspection.

forge new

Creates a new project from a selected template. Accepts project name, template type, and Nexus pull flag. Renders the template directory, writes project metadata, initializes git, and optionally sets a remote origin.

forge doctor

Validates local development prerequisites: git, Python version, Docker, and other template-specific requirements. Outputs a pass/fail checklist. Supports --json for machine-readable output.

forge project inspect

Inspects an existing project directory for conformance to Forge's expected structure. Reports missing files, metadata status, and structural drift. Supports --json for CI integration.

Nexus artifact commands

forge template package, publish, pull, list, and info integrate with a Nexus raw repository for template versioning, distribution, and discovery.

Schema-driven generation

Templates are rendered from a manifest-driven structure. Each template directory contains the file tree, metadata schema, and documentation stubs. Rendering is deterministic and repeatable.

Generated-project evidence

The SRE Log Pipeline was scaffolded from Forge's python-worker template. That project reached v0.2.0 with 8 test files, a Jenkinsfile, and a StarkGrid adapter — demonstrating that Forge-generated structure is production-discipline-ready.

Templates

Three templates covering the primary project types.

python-worker Python service or pipeline worker. Includes pyproject.toml, test structure, Dockerfile, Jenkinsfile, and release runbook. Used to scaffold SRE Log Pipeline.
java-spring-service Spring Boot service. Includes Maven POM, test structure, Dockerfile, and Jenkinsfile. Consistent with StarkGrid module conventions.
node-dashboard Node.js frontend or dashboard project. Includes package.json, Vite or equivalent build config, and static export structure.

Proof evidence

28 tests, a tagged release, and a generated downstream project.

Forge has 28 tests covering CLI behavior, template rendering, doctor validation, Nexus artifact commands, and project inspection. The test suite runs without external dependencies.

The proof is not limited to the tool itself. The SRE Log Pipeline — a downstream project scaffolded from Forge's python-worker template — reached its own v0.2.0 release with incident evidence schema v1.0, a StarkGrid adapter, and 8 test files. That downstream maturity validates the template's structural discipline.

Supporting project · Forge MCP · v0.1.1

Read-only MCP server for Forge repository knowledge.

Forge MCP is a read-only Model Context Protocol server that exposes Forge's templates, validation commands, project structure, and documentation to AI clients. It was built to let AI tools assist with Forge usage without granting write access, execution authority, or access to private project content.

The server implements a 10-tool contract validated by a dedicated contract test. Any addition, removal, or rename of a tool is a breaking change that must fail the contract test first.

Integration boundary

  • Forge MCP reads Forge's template files and documentation; it does not write, create projects, or execute commands.
  • All tools are read-only. The contract test (test_tool_contract.py) enforces the exact tool name set.
  • Request validation prevents malformed inputs from reaching the filesystem.
  • Responses are bounded to prevent context overflow.

Current maturity

Current limitations

What Forge does not claim.