lang-generic

Detect project language and infer public APIs using heuristic patterns.

6|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/xiaolai/docs-guardian-for-claude --skill lang-generic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lang-generic
Source: https://github.com/xiaolai/docs-guardian-for-claude/tree/main/skills/docs-guardian/languages/generic
Command: npx skills add https://github.com/xiaolai/docs-guardian-for-claude --skill lang-generic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When language/grammar is unknown or unsupported, this adapter provides a best-effort mechanism to identify the project language and infer a reasonable public API visibility model using heuristic signals.

Core Features & Use Cases

  • Language detection through marker cues and file-level hints across diverse ecosystems
  • Symbol and visibility inference using language-agnostic patterns for functions, classes, and types
  • Documentation-pattern recognition to surface lightweight metadata about public interfaces
  • Use Case: integrate into an analysis pipeline to propose a mapping from code to docs for projects with unknown tech stacks

Quick Start

Use the generic language adapter to identify the project's language and apply heuristic-based public API detection.

Frequently Asked Questions about lang-generic

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

FAQPage Schema
How do I detect public APIs in a project when the programming language is unsupported?

To detect public APIs in unsupported languages, you can use a heuristic-based language adapter that examines marker cues, symbols, and documentation patterns to infer public interfaces without relying on language-specific parsers.

What is heuristic-based symbol detection for unknown tech stacks?

Heuristic-based symbol detection is a mechanism that infers functions, classes, and types by examining language-agnostic patterns and file-level hints, providing a best-effort visibility model for projects with unknown tech stacks.

How do I infer documentation metadata without using a dedicated language parser?

You infer documentation metadata by recognizing documentation patterns and doc-comment cues across diverse ecosystems, using language-agnostic analysis to surface lightweight metadata about public interfaces.

Can I identify a project's programming language using only marker cues and file hints?

Yes, you can identify a project's programming language by analyzing marker cues and file-level hints across diverse ecosystems, enabling language detection even when the grammar is completely unknown.

What are the limitations of using language-agnostic patterns for API visibility inference?

The limitation of using language-agnostic patterns for API visibility inference is that it provides only a best-effort, heuristic-based approximation rather than the precise analysis guaranteed by dedicated language-specific parsers.