메뉴
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명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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.