github wiki plan links and category indexes - tfsugjp/skills GitHub Wiki

GitHub Wiki Plan Links and Category Indexes

日本語

Tracking issue: #61

Sub-issues:

Background

The repository Wiki stores plan files under dated Git paths such as plan/2026-09-20/, while GitHub publishes Wiki pages in a flat public namespace. Home links that include the Git directory therefore lead to 404 pages. The plan workflow needs one canonical public route for every page and a category-based Home index in both languages.

Design

  • Use the page basename without the .md suffix or dated Git directory for Wiki-internal links. For example, plan/2026-09-23/example.md is linked as example.
  • Keep English and Japanese pages as a one-to-one pair using the _ja suffix and reciprocal language links.
  • Group Home and Home_ja entries under category headings, with matching rows and tracking issue links.
  • Treat the Date column as the latest content update date for the plan. Updating only Home navigation does not advance that date.
  • Detect duplicate basenames across all dated directories before publishing, because the public Wiki route is flat.

Implementation

  1. Update the github-wiki-plan skill and templates with canonical flat routes, category table rules, collision checks, and date semantics.
  2. Extend validation for nested paths, .md targets, missing pages, duplicate basenames, and bilingual Home consistency.
  3. Repair the existing Home and Home_ja pages, add this plan under Documentation & Workflow, and fix the existing repository-init links.

Verification

  • Resolve every internal link in both Home pages against the set of Wiki page basenames.
  • Confirm no Home or plan link contains / or ends in .md.
  • Confirm the English and Japanese Home rows use the same plan date and reciprocal page routes.
  • Open each plan route and language-switch route after publishing, including repository-init and this plan.

Reference format: vsextensionforcodex Wiki.

⚠️ **GitHub.com Fallback** ⚠️