init

Discover .NET project values and replace configuration token placeholders.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/geobarteam/github-copilot-configs --skill init-geobarteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/geobarteam/github-copilot-configs/tree/main/skills/init
Command: npx skills add https://github.com/geobarteam/github-copilot-configs --skill init-geobarteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializes and re-initializes Copilot and GitHub configuration by discovering project-specific values and replacing placeholder tokens, removing manual, error-prone edits across multiple config files.

Core Features & Use Cases

  • Automated Discovery: Detects solution name, namespace root, DbContext class, test executable path, architecture type, and localhost ports from csproj files and launchSettings.json.
  • Safe Token Replacement: Replaces token placeholders in designated .github and root config files with confirmation, preserves examples, and reports remaining unreplaced tokens.
  • State Management & Re-init: Creates or updates .copilotrc.json, shows diffs on re-run, and only updates files when values change; ideal after importing templates, renaming projects, or auditing config state.

Quick Start

Run the init skill to auto-detect the solution structure and replace token placeholders in the repository's .github configuration files.

Frequently Asked Questions about init

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

FAQPage Schema
How do I automate token replacement in .NET GitHub configuration files?

To automate token replacement in .NET GitHub configuration files, run the init skill to detect solution name, namespace root, DbContext, test paths, and localhost ports from csproj and launchSettings.json. It updates designated .github and root config files with confirmation and reports unreplaced tokens.

What is the best way to initialize Copilot configuration for a Blazor WebAssembly solution?

Initializing Copilot configuration for a Blazor WebAssembly solution involves scanning project files and launchSettings.json to discover architecture type and localhost ports. The init skill creates or updates a .copilotrc.json state file and replaces placeholder tokens in imported GitHub configuration templates.

Can I reinitialize Copilot tokens after renaming my .NET project?

You can reinitialize Copilot tokens after renaming a .NET project by rerunning the init skill. It displays diffs on re-run and only updates .github and root config files when discovered values change, ensuring your repository configuration stays synchronized with the new project structure.

Does the init skill require manual input for missing .NET solution metadata?

The init skill prompts for missing values when automated discovery cannot detect solution name, namespace root, DbContext class, or test executable paths from csproj files and launchSettings.json. It performs file system scans to gather metadata before updating the designated configuration files.

Are there limitations when replacing placeholder tokens in .NET repository config files?

A key limitation of replacing placeholder tokens in .NET repository config files is that the init skill only modifies designated .github and root config files. It preserves examples and reports remaining unreplaced tokens, but does not edit arbitrary source files outside the designated configuration scope.