skills.rest
nacos-group
nacos-groupOFFICIAL
Explore all skills by this author →
GitHub

nacos-doc-feedback

Parses Content Source URLs to locate and edit matching doc files across zh-cn and en versions.

115|205|Updated Jul 20, 2018
Search Tags:#versioning#feedback#documentation#localization#multilingual#content-management#nacos
One-click install
npx skills add https://github.com/nacos-group/nacos-group.github.io --skill nacos-doc-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nacos-doc-feedback
Source: https://github.com/nacos-group/nacos-group.github.io/tree/main/.agents/skills/nacos-doc-feedback
Command: npx skills add https://github.com/nacos-group/nacos-group.github.io --skill nacos-doc-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps locate the original documentation files referenced in feedback blocks by parsing Content Source URLs, resolves both zh-cn and en counterparts, and applies maintainer suggestions with version-scoped edits.

Core Features & Use Cases

  • URL-to-path resolution: Converts Content Source URLs into local repository paths under src/content/docs.
  • ** bilingual pairing & versioning**: Identifies corresponding en/zh-cn documents across v3.0/next/latest and maintains parity.
  • Edit application: Applies structured feedback to matched documents while preserving frontmatter and links.

Quick Start

Provide a feedback block containing a Content Source URL to trigger path resolution and cross-language edits across relevant versions.

Frequently Asked Questions about nacos-doc-feedback

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

FAQPage Schema
How do I automate Nacos documentation feedback triage across multiple versions?▼

Nacos documentation feedback triage is automated by parsing Content Source URLs to locate repository files and applying version-scoped edits to align content across v3.0, next, and latest.

How do I resolve Content Source URLs to local paths for Nacos content management?▼

Content Source URL resolution converts web links into local repository paths under src/content/docs, enabling direct navigation and structured edits to matched documentation files.

Does this approach maintain language parity for zh-cn and en Nacos docs?▼

Language parity is maintained for zh-cn and en Nacos docs by automatically identifying corresponding bilingual counterparts and applying feedback suggestions to both versions simultaneously.

Can I apply structured feedback to Nacos docs while preserving frontmatter and links?▼

Structured feedback can be applied to Nacos docs while preserving frontmatter and links, ensuring safe and consistent updates to matched documentation files across versions.

What is the best way to handle multilingual Nacos documentation edits across different versions?▼

Handling multilingual Nacos documentation edits is best done by parsing Content Source URLs to resolve bilingual pairs and applying version-scoped edits to maintain language parity and consistency.

Related Skills

Explore More Content & Communication Skills→
1479089714790897
7

kwp-engineering-code-review

Analyze source code for security vulnerabilities, performance bottlenecks, and maintainability issues from pull request URLs or local file paths.

Community
Advanced
nacos-groupnacos-group
115

nacos-doc-sync-en

Mirror zh-cn documentation changes to English en counterparts in structured repositories.

Official
Intermediate
gnektgnekt
3.4k

vault-audit

Audit Obsidian vaults across seven phases for structure, links, and frontmatter.

Community
Advanced
steedossteedos
1.6k

steedos-translations

Translate Steedos metadata into English and Simplified Chinese translation files.

Official
Intermediate