// Use when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns.
| name | lang-generic |
| description | Use when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns. |
Used when the project language is not recognized or not in the supported set. Applies best-effort heuristics.
Since we don't know the language's visibility rules, use these signals:
| Signal | Likely Public | Confidence |
|---|---|---|
export keyword present | Yes | High |
public keyword present | Yes | High |
pub keyword present | Yes | High |
| Uppercase first letter (Go-like) | Maybe | Medium |
| No underscore prefix | Maybe | Low |
| Defined at top-level / module scope | Likely | Medium |
Look for common patterns across languages:
| Pattern | Likely Symbol Type |
|---|---|
function name( or func name( or def name( or fn name( | Function |
class Name | Class |
struct Name | Struct |
interface Name | Interface |
type Name | Type definition |
enum Name | Enum |
const NAME or val NAME or let NAME (UPPER_CASE) | Constant |
Look for common doc comment patterns:
| Pattern | Format |
|---|---|
/** ... */ | JSDoc / JavaDoc |
/// ... | Rust-style / C# XML doc |
# ... after """ | Python docstring |
// Name ... (comment starting with symbol name) | Godoc-style |
""" ... """ or ''' ... ''' | Python docstring |
Since we can't parse language-specific documentation format, use a simpler check:
When using the generic adapter, the agent should:
language explicitly in configSource files: all files not matching known binary/config extensions
Exclude: common non-source directories (node_modules/, vendor/, dist/, .git/)
Use when generating or auditing documentation in Docusaurus format — covers config, directory structure, frontmatter conventions, and build commands.
Use when generating or auditing documentation in MkDocs format — covers config, directory structure, frontmatter conventions, and build commands.
Use when generating or auditing documentation in plain Markdown format — covers config, directory structure, frontmatter conventions, and build commands.
Use when generating or auditing documentation in Sphinx format — covers config, directory structure, frontmatter conventions, and build commands.
Use when generating or auditing documentation in VitePress format — covers config, directory structure, frontmatter conventions, and build commands.
Use when writing, auditing, or generating documentation for Go projects — covers docstring conventions, API doc extraction, and Go-specific patterns.