gitea/skills/wiki/SKILL.md

name, description

name	description
wiki	Read or write a Gitea wiki page through tools/gitea.sh and tools/hash-id. Resolve the wiki repo per page type with JSC_WIKI_REPO_{TYPE} first, then JSC_WIKI_REPO, and ask only when neither is set. Page content is chart-first - prefer mermaid diagrams and markdown tables over plain prose. Used by jsc-ask, jsc-sdlc, and jsc-log for wiki pages, including ERROR pages, not for repo code files.

wiki — read and write Gitea wiki pages

Every wiki operation in the jsc skill set goes through this skill. One entry point, one permission path.

Resolve the wiki location

Different page types can live in different {owner}/{repo} repos, classified by page-name prefix: QUESTION, PLAN, ANALYZE, MAINTAIN, REPO, LOG, LEARN, ERROR.

1. Before asking the user, inspect the current shell environment for the needed repo variables and Gitea connection variables: JSC_WIKI_REPO_{TYPE}, JSC_WIKI_REPO, GITEA_HOST, and GITEA_TOKEN (also check tea login list for a usable login token when GITEA_TOKEN is unset). Use inherited shell values first; only ask when the needed repo or connection value cannot be resolved after that check. GITEA_HOST and GITEA_TOKEN are both covered by this ask-if-unresolvable rule, the same as the wiki-repo variables below.
2. Run tools/gitea.sh wiki-repo {TYPE} (TYPE = the page-name prefix). Allowed types are QUESTION, PLAN, ANALYZE, MAINTAIN, REPO, LOG, LEARN, and ERROR. Resolution order is JSC_WIKI_REPO_{TYPE} first, then JSC_WIKI_REPO. Never borrow another type's repo.
3. On exit 3 (neither is set after env inspection), ask the user for that page type's {owner}/{repo} per the jsc-ask:ask rules, and suggest setting JSC_WIKI_REPO_{TYPE} (can differ per type) or JSC_WIKI_REPO (shared default).

Operations

Action	Command
list pages	tools/gitea.sh wiki-list {owner}/{repo}
read page	tools/gitea.sh wiki-get {owner}/{repo} {page} (exit 4 when missing)
write page	write the content to a temp file first, then tools/gitea.sh wiki-put {owner}/{repo} {page} {file} (creates or updates automatically)

Rules

1. Page names must follow the wiki naming table in the skill guidelines (see jsc-meta/references/guidelines.md).
2. Use tools/hash-id for {HASH} values. It returns the first 8 uppercase SHA-1 hex chars, or H plus the first 7 chars when the raw hash starts with 0-9, A, B, or C.
3. To update a contents page (*_CONTENTS): wiki-get it first, apply the template to append or modify, then wiki-put the whole page back. Never overwrite entries owned by others.
4. Write all wiki content in UTF-8 Traditional Chinese, per the STE100 output rule.
5. Prefer visual forms for page content: use mermaid diagrams (flowchart, sequence, gantt, pie) and markdown tables wherever the information allows. Plain running text is the last resort, kept short.
6. Authentication fallback is built into tools/gitea.sh: on a missing GITEA_TOKEN or a 401/403 response it retries with the tea CLI login token automatically. But before calling it, resolve GITEA_HOST and GITEA_TOKEN per rule 1: if GITEA_HOST is unresolvable, or GITEA_TOKEN is unset and no tea login token exists either, ask the user for the missing value per the jsc-ask:ask rules — same decision-tree pattern as the missing-wiki-repo case above — before calling tools/gitea.sh. Only report a genuine failure when the user has no answer to give or Gitea itself rejects the request (e.g. a 401/403 even after the tea fallback).