Agent skill
publish-wiki
Publish pending changes in the sibling hmis.wiki repository to GitHub. Use when wiki documentation has been created or edited in the sibling ../hmis.wiki directory and needs to be committed and pushed to https://github.com/hmislk/hmis/wiki.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/publish-wiki
SKILL.md
Publish to GitHub Wiki
Commit and push pending changes in the sibling ../hmis.wiki repository to the GitHub Wiki.
IMPORTANT: Wiki files live ONLY in the sibling ../hmis.wiki directory. Do NOT create wiki markdown files inside the main project repository (no wiki-docs/ folder) - this causes git submodule issues.
Steps
-
Check if sibling wiki directory exists:
bashtest -d "../hmis.wiki" && echo "EXISTS" || echo "NOT_FOUND" -
If NOT_FOUND, clone the wiki repo:
bashcd .. && git clone https://github.com/hmislk/hmis.wiki.git && cd hmis -
Pull latest changes:
bashcd ../hmis.wiki && git pull origin master -
Check for pending changes:
bashcd ../hmis.wiki && git status -
If there are changes, commit and push:
bashcd ../hmis.wiki git add . git commit -m "Add/update wiki documentation Co-Authored-By: Claude <[email protected]>" git push origin master -
Report published pages with wiki URLs:
https://github.com/hmislk/hmis/wiki/Page-Name
Important Notes
- Wiki page names come from file names (dashes become spaces)
- Always pull latest wiki before committing to avoid conflicts
- Publish IMMEDIATELY after creating docs, don't wait for PR merge
- All wiki content is in
../hmis.wiki- NEVER in the main project repo
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?