メニュー
Manage GitHub Wiki and GitHub Projects for the current repo. Knows the authentication quirks for each (SSH for Wiki push, OAuth scopes for Projects).
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/PrairieAster-Ai/nearest-nice-weather --skill github-wikiコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Structural code-health metrics, the rolled-up CodeHealth score, and the Code Health Dashboard pipeline (Maintainability Index, cyclomatic/cognitive complexity, churn×complexity hotspots, coupling/instability, change-coupling, duplication, circular imports). Measures + trends + renders; the quality-butler composes it. Use to instrument a repo, take a reading, or refresh the dashboard.
Assess and improve code quality in TypeScript/React projects. Runs lint, type-check, coverage, duplication, and complexity analysis with sprint planning.
Make code readable for humans, IDEs, doc generators, and AI at once — by enforcing a TSDoc-native comment standard and turning those comments into GitHub Wiki documentation (cross-linked to the source). Use to assess doc-comment coverage, annotate a file/area with quality docs, or generate + publish project docs. TypeScript/React/MUI first; also covers HTML (semantic/ARIA), CSS/Sass (KSS/SassDoc), and vanilla JS (JSDoc) — see references/comment-style.md.
SKILL.md を表示中
SOC 職業分類に基づく
| name | github-wiki |
| description | Manage GitHub Wiki and GitHub Projects for the current repo. Knows the authentication quirks for each (SSH for Wiki push, OAuth scopes for Projects). |
| argument-hint | [wiki or projects] [action] |
| allowed-tools | Bash(git:*),Bash(gh:*),Bash(ssh:*),Read,Write,Edit,Grep,Glob |
Assists with GitHub Wiki editing and GitHub Project board management for the current repository.
/github-wiki wiki list — Clone the wiki and list all pages/github-wiki wiki edit <page> — Edit a specific wiki page/github-wiki wiki create <page> — Create a new wiki page/github-wiki projects list — List GitHub Projects for this repo/github-wiki projects view <number> — View a specific project boardGitHub uses three different auth mechanisms depending on the operation. Getting these wrong produces confusing 403 errors.
| Operation | Auth method | Notes |
|---|---|---|
| Wiki read (clone) | SSH or HTTPS | Either works |
| Wiki push | SSH only | Fine-grained PATs get 403. Always use git@github.com: URL. |
| Issues, PRs, releases | gh CLI | Uses the OAuth token from gh auth login |
| GitHub Projects (boards) | gh CLI + project scope | Requires gh auth refresh -s read:project,project first |
ssh -T git@github.comgit remote get-url origin.git with .wiki.git and ensuring it starts with git@github.com:/tmp/ on Linux/macOS, %TEMP% on Windows)The default gh OAuth token lacks project scopes. If gh project list fails with a scopes error, tell the user:
Your
ghtoken needs theprojectscope. Run:gh auth refresh -s read:project,project
git clone git@github.com:<owner>/<repo>.wiki.git <scratchpad-or-temp-dir>/<project>-wiki
git -C <wiki-dir> add . && git -C <wiki-dir> commit -m "docs: <description>" && git -C <wiki-dir> push origin master
Wiki repos have a single master branch and no PR workflow — commits push directly.
Detect the repo owner from gh repo view:
OWNER=$(gh repo view --json owner --jq '.owner.login')
# List projects
gh project list --owner "$OWNER"
# View a project
gh project view <number> --owner "$OWNER"
# Add an issue to a project
gh project item-add <project-number> --owner "$OWNER" --url <issue-url>
gh auth refresh -s read:project,project.master, not main.git pull before editing if the clone already exists.