skills.rest
GetGet99
GetGet99COMMUNITY
Explore all skills by this author →
GitHub

quickmarkup-contributing

Map QuickMarkup repository areas to files for contributor edits.

4|Updated Jan 16, 2026
Search Tags:#repository#diagnostics#codegen#language#contribute#binders#quickmarkup
One-click install
npx skills add https://github.com/GetGet99/QuickMarkup --skill quickmarkup-contributing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quickmarkup-contributing
Source: https://github.com/GetGet99/QuickMarkup/tree/main/.cursor/skills/quickmarkup-contributing
Command: npx skills add https://github.com/GetGet99/QuickMarkup --skill quickmarkup-contributing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributors to QuickMarkup need a clear map of where to edit language definitions, AST structures, binders, code generation, and Roslyn analyzers inside the repository, reducing guesswork and integration errors.

Core Features & Use Cases

  • Provides a centralized map of source areas (e.g., QuickMarkup.Language, QuickMarkup.SourceGen) to modify language rules, AST nodes, binders, diagnostics, and generated C# output.
  • Helps contributors locate the exact files for implementing new features or fixing core tooling, ensuring changes align with repository structure and guidelines.

Quick Start

Navigate to the QuickMarkup repository and follow the mapped file references to edit language, AST, binders, or codegen files.

Frequently Asked Questions about quickmarkup-contributing

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

FAQPage Schema
How do I find the right files to edit when adding new AST nodes to QuickMarkup?▼

Locating files for AST nodes in QuickMarkup involves navigating the QuickMarkup.Language directory via repository file maps, pinpointing exact source files for modifying AST structures and language definitions.

Where are Roslyn analyzers and diagnostics implemented in the QuickMarkup repository?▼

Diagnostics and Roslyn analyzers in QuickMarkup are implemented by editing files mapped within core language tooling directories, enforcing repository-relative paths to ensure correct integration.

What is the best way to contribute new syntax rules to QuickMarkup core tooling?▼

Contributing syntax rules to QuickMarkup requires editing files in the QuickMarkup.Language directory, using a centralized map to locate areas and reduce integration errors.

How do I map code generation areas when contributing to QuickMarkup source generation?▼

Mapping code generation areas for QuickMarkup contributions centers on the QuickMarkup.SourceGen directory, guiding you to correct files for implementing generated C# output.

Can I use this guidance for consuming QuickMarkup as a library in my own project?▼

This guidance does not apply to consuming QuickMarkup as a library; it exclusively maps repository areas for contributors actively editing the QuickMarkup core, binders, and codegen.

Why do I need repository-relative path guidance when modifying QuickMarkup binders?▼

Repository-relative path guidance is needed when modifying QuickMarkup binders to ensure changes align with repository structure, preventing guesswork and integration errors across core directories.

Related Skills

Explore More Software Engineering Skills→
Soul-Brews-StudioSoul-Brews-Studio
116

project

Manage external GitHub repositories across local ghq clones and remote GitHub.

Official
Advanced
CoolCoderSuperCoolCoderSuper
4

analyzer-codefix

Create and maintain Roslyn analyzers, code fixes, and refactorings for C# and VB projects.

Community
Advanced
AGIBuildAGIBuild
10

dotnet-csharp-source-generators

Create and consume Roslyn source generators in .NET with incremental patterns.

Community
Advanced
gmh5225gmh5225
868

llvm-tooling

Create LLVM/Clang-based tools for source analysis, transformation, and IDE integration.

Community
Advanced