Create New Wiki Page
- 13 installs
- 21 repo stars
- Updated July 31, 2026
- jim60105/copilot-prompt
Create a new Azure DevOps wiki page in Traditional Chinese, place it correctly in the tree with mermaid diagrams, update .order, and commit.
About
Guides writing a new Azure DevOps wiki page after reading existing project docs, adding mermaid diagrams and FAQs, and registering it in the .order and category files. A developer uses it to extend project documentation in an Azure DevOps wiki.
- Reads design/requirements docs before drafting to keep context consistent
- Updates .order and category markdown, then commits with a good message
Create New Wiki Page by the numbers
- 13 all-time installs (skills.sh)
- Ranked #1,103 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jim60105/copilot-prompt --skill create-new-wiki-pageAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 13 |
|---|---|
| repo stars | ★ 21 |
| Last updated | July 31, 2026 |
| Repository | jim60105/copilot-prompt ↗ |
What it does
Create a new Azure DevOps wiki page in Traditional Chinese, place it correctly in the tree with mermaid diagrams, update .order, and commit.
Files
Create New Wiki Page
Create a new Azure DevOps wiki page with proper structure and formatting.
Steps
1. Execute tree . /f in pwsh to get all the page lists.
2. Read all docs under 設計文件, 功能需求, 標準規範 or other documents to get the full view of the project.
3. Plan the content for the wiki page about the user's specified topic. ${input:what-to-write-in-this-page}.
4. Include a mermaid diagram on the page if there is suitable content for it.
5. If the user doesn't specify a location, find an appropriate category and path for this page.
6. Write the page in 正體中文.
7. Add this page to the .order file in the same directory.
8. Add this page to the category's markdown file (e.g., if under 標準規範/, update 標準規範.md).
9. Review whether the Azure DevOps Wiki page is well-written; refine it to improve quality.
10. Git commit with a good message body.
11. Summarize what was done.
Wiki Writing Guidelines
- Write in simple, concise language.
- Follow a consistent format across all pages.
- Break up sections with headlines, subheads, and text boxes.
- Enrich pages with mermaid diagrams and links.
- Include a list of FAQs in each section.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71