skills.rest
nist0
nist0COMMUNITY
Explore all skills by this author →
GitHub

cli-platform-analysis

Analyze .NET CLI platform projects and generate project-context documentation.

Updated Apr 9, 2026
Search Tags:#static analysis#CLI#document generation#project context#.NET
One-click install
npx skills add https://github.com/nist0/CoDev --skill cli-platform-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-platform-analysis
Source: https://github.com/nist0/CoDev/tree/main/.github/skills/cli-platform-analysis
Command: npx skills add https://github.com/nist0/CoDev --skill cli-platform-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of performing a comprehensive static analysis of a .NET CLI platform project, producing a detailed documentation file that serves as a living context for all subsequent engineering tasks.

Core Features & Use Cases

  • Static Analysis: Analyzes GitHub workflows, infrastructure configurations, solution structure, CLI surface, test projects, and existing documentation.
  • Project Context Documentation: Generates a single document (docs/project-context.md) containing the analysis results.
  • Use Case: When starting a new CLI platform project or after significant changes, this Skill provides a quick overview of the project's current state.

Quick Start

Run the cli-platform-analysis skill within the project root to generate the docs/project-context.md file.

Frequently Asked Questions about cli-platform-analysis

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

FAQPage Schema
What does static analysis of a .NET CLI platform solution structure include?▼

Static analysis for .NET CLI platforms examines GitHub workflows, infrastructure configurations, solution structure, CLI surface, test projects, and existing documentation to produce a comprehensive project context file.

When should I run static analysis to generate project context for my CLI platform?▼

Run static analysis to generate project context when starting a new .NET CLI platform project or after significant changes, providing a quick overview of the project's current state for engineering tasks.

Do I need specific analysis tools to perform .NET CLI platform static analysis?▼

Performing .NET CLI platform static analysis requires specific analysis tools and an understanding of .NET CLI platform projects to successfully evaluate the solution structure and generate documentation.

What is the best way to document GitHub workflows and infrastructure in a .NET project?▼

The best way to document GitHub workflows and infrastructure is to automate static analysis of the .NET project, which consolidates configurations, CLI surface, and test projects into a single project context document.

How does CLI surface analysis integrate with existing .NET test project documentation?▼

CLI surface analysis integrates with existing .NET test project documentation by evaluating both during the static analysis process, combining them into a unified project context markdown file for engineering reference.

Related Skills

Explore More Software Engineering Skills→
SzantoiSzantoi

dotnet-upgrade

Automate .NET framework project upgrades with analysis, execution, and validation.

Community
Advanced
hathbangerhathbanger

search

Search GTM knowledge bases using semantic, keyword, and hybrid queries.

Community
Advanced
briangrebriangre
1

create-cloud-flow

Automate deployment and management of Power Automate cloud flows in Power Platform solutions.

Community
Intermediate
AGIBuildAGIBuild
10

dotnet-solution-navigation

Parse .sln/.slnx files and map project dependencies in .NET solutions.

Community
Intermediate