30 lines
1.8 KiB
Markdown
30 lines
1.8 KiB
Markdown
---
|
|
name: wiki
|
|
description: Read or write a Gitea wiki page through tools/gitea.sh with GITEA_TOKEN. Resolve the wiki repo per page type (QUESTION/PLAN/ANALYZE/MAINTAIN/REPO/LOG) via gitea.sh wiki-repo, falling back to JSC_WIKI_REPO or a decision-tree question. Used by jsc-ask, jsc-sdlc, and jsc-log for all wiki 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`.
|
|
|
|
1. Run `tools/gitea.sh wiki-repo {TYPE}` (TYPE = the page-name prefix). Resolution order: `JSC_WIKI_REPO_{TYPE}` > `JSC_WIKI_REPO`. When either is set, use it and skip the question.
|
|
2. On exit 3 (neither is set), 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. 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.
|
|
3. Write all wiki content in UTF-8 Traditional Chinese, per the STE100 output rule.
|