greenfield-baseline

Name: greenfield-baseline
Availability: InStock
Author: mcj-coder

Automate project scaffolding with quality gates, CI/CD, and repository structure.

1|1|Updated Jan 3, 2026

Search Tags:#ci/cd #development standards #project setup #quality gates #greenfield #repository structure

Ready to run

npx skills add https://github.com/mcj-coder/development-skills --skill greenfield-baseline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: greenfield-baseline
Source: https://github.com/mcj-coder/development-skills/tree/main/skills/greenfield-baseline
Command: npx skills add https://github.com/mcj-coder/development-skills --skill greenfield-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures new projects start with a robust foundation, preventing technical debt by establishing quality gates, proper repository structure, CI/CD, and development standards before any feature work begins.

Core Features & Use Cases

Project Foundation: Sets up essential project elements like directory structure, README, and contribution guidelines.
Quality Gates: Integrates linting, formatting, spelling checks, and pre-commit hooks.
CI/CD Setup: Configures a basic CI pipeline for automated checks.
Use Case: When starting a brand new microservice, this skill will automatically create the necessary directories, set up ESLint and Prettier for a Node.js project, configure a GitHub Actions workflow, and ensure a CONTRIBUTING.md is in place.

Quick Start

Use the greenfield-baseline skill to set up a new .NET API project with a proper foundation.

Frequently Asked Questions about greenfield-baseline

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

FAQPage Schema

How do I set up a new software project foundation from scratch?▼

Setting up a new project foundation involves automating essential scaffolding like directory organization, configuration files, CI/CD pipelines, and quality tooling before feature development begins.

What quality gates should I include in a greenfield repository structure?▼

Quality gates for a greenfield repository should integrate linting, formatting, spelling checks, and pre-commit hooks to prevent technical debt and ensure development standards are met.

How do I configure CI/CD and development standards for a new microservice?▼

Configuring CI/CD and development standards for a new microservice requires establishing a basic CI pipeline for automated checks alongside contribution guidelines to maintain code quality.

Can I use this project setup approach for a .NET API or Node.js project?▼

Yes, this project setup approach works for a .NET API or Node.js project by automatically creating necessary directories, configuring ESLint and Prettier, and establishing a proper foundation.

Why do I need development standards and quality gates before feature development?▼

Development standards and quality gates are needed before feature development to ensure new projects start with a robust foundation, actively preventing technical debt from accumulating early in the lifecycle.