Aspose.PDF-Documentation

Audit Hugo Markdown documentation front matter for required keys, duplicate keys, duplicate URLs, YAML style hazards, URL shape, `type: docs`, integer weights, quoted `lastmod` dates, trailing whitespace, and missing `linktitle` values. Use this skill when a user asks to check, validate, lint, repair, or batch-scan Hugo front matter in Markdown docs, especially content repositories with language/product trees. When multiple issue types are present in a single file, report and resolve them in this order: (1) required-key defects, (2) YAML-style hazards, (3) URL or weight issues flagged for manual review, (4) recommended-key recommendations. Do not apply auto-fixes to files with unresolved `url`, duplicate URL, or `weight` issues until the user confirms.

Analyze Hugo Markdown front matter for documentation pages and add or repair missing SEO metadata fields, especially AlternativeHeadline, Abstract, and TechArticle. Use this skill when a user wants Codex to audit docs front matter, fill missing article metadata, or normalize these fields across a section of a docs repository.

Audit Markdown documentation in the en/java section for style and formatting issues, then apply safe fixes to Markdown structure and Java fenced code blocks. Use this skill when a user wants Codex to review Java documentation pages, normalize Markdown layout, or clean up Java examples without rewriting the article content.

Install a Python formatter, preferably Ruff, and then verify it can be used for formatting checks and fixes. Use this skill when a formatter is missing and Codex needs to bootstrap Ruff or Black before running Python format checks.

Check Python source formatting and fix formatting issues automatically in both Python files and Markdown pages that contain Python fenced code blocks. Use this skill when a user wants Codex to audit Python files, normalize Python code snippets inside documentation pages, or apply the project-preferred formatter to either kind of content.

Use this skill when reviewing or editing Russian technical documentation with numbered or step-by-step instructions. It normalizes Russian steps to polite imperative action-verb style.