write-wiki

Create user documentation for the HMIS wiki following writing guidelines. Use when creating documentation for end users (pharmacy staff, nurses, doctors, administrators). Creates documentation directly in the sibling ../hmis.wiki directory.

Jump to install

Repository: hmislk/hmis
Last source activity: February 10, 2026 at 08:39
Detected SKILL.md language: English
Stars: 228
Forks: 137

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/hmislk/hmis --skill write-wiki

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

demonstrate-issues

Run a live bug-demonstration capture session before filing GitHub issues. The user drives the browser and narrates bugs one after another ("see this — clicking X should do Y but does Z"); this skill captures each demo (snapshot + screenshot + description + environment context) without investigating, only after the user signals the session is over does it investigate root causes, then only after the user reviews the write-ups does it file issues. Use when asked to "demonstrate some bugs", "show you issues before filing them", or via `/demonstrate-issues`. Never fixes anything — it ends at filing GitHub issue(s); any actual fix is separate, later `dev-issue` work.

2026-08-23

dev-issue

Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and the database, iterate until passing, record any testing-workflow learnings, commit/push, open a PR, and loop on review comments until mergeable. Use when asked to "take issue #N end to end", "do issue #N fully", "develop and ship issue #N", or similar full-cycle requests.

2026-08-23

dev-issue-unattended

Run one or more GitHub issues through their full lifecycle end-to-end with NO pauses for user input — investigate, decide the approach, gather test context, and run the CI/review loop entirely autonomously, documenting every judgment call for after-the-fact review instead of asking. Accepts a single issue, a batch of issue numbers/URLs, or an unfiled bug/request described in plain text. Use ONLY when the user has explicitly said they will be unreachable (away from the computer, asleep, offline) and wants the issue(s) shipped as mergeable PR(s) without them. Do not use this for normal work — use dev-issue instead, which asks for input at the same points this skill auto-resolves.

2026-08-23

View all from this repository

name	write-wiki
description	Create user documentation for the HMIS wiki following writing guidelines. Use when creating documentation for end users (pharmacy staff, nurses, doctors, administrators). Creates documentation directly in the sibling ../hmis.wiki directory.
disable-model-invocation	true
allowed-tools	Read, Write, Glob, Grep, Bash
argument-hint	[module/Feature-Name]

Write Wiki Documentation

Create end-user documentation directly in the sibling ../hmis.wiki directory following the project's wiki writing guidelines.

IMPORTANT: Wiki files live ONLY in the sibling ../hmis.wiki directory. Do NOT create wiki markdown files inside the main project repository - this causes git submodule issues.

Arguments

$0 - Module and feature name (e.g., Pharmacy/Stock-Transfer)

Target Audience

Pharmacy staff, nurses, doctors, administrators
Non-technical healthcare professionals
Focus on how to use features, not implementation details

Required Structure

Every wiki page must include these sections:

Overview - What the feature does and why (2-3 sentences)
When to Use - Specific scenarios and business triggers
How to Use - Step-by-step with navigation paths
Understanding Messages - Success, warning, and error messages
Best Practices - Tips for effective use
Troubleshooting - Common problems and solutions
Configuration (Admin) - Settings that affect the feature
FAQ - Common questions

Writing Rules

Active voice: "Click the Submit button" (not "The button should be clicked")
Imperative mood: "Enter the patient ID"
Bold UI elements: Pharmacy > Reports > Stock Ledger
One action per step in numbered procedures
No code, no technical details - no Java classes, SQL, file paths, or method names

What NOT to Include

Code snippets, file paths, line numbers
Java class names, method signatures
Database schema or SQL queries
JSF component IDs or backend beans
Developer debugging information

File Location

Create files at: ../hmis.wiki/$0.md

Ensure the wiki repo exists first:

test -d "../hmis.wiki" || (cd .. && git clone https://github.com/hmislk/hmis.wiki.git && cd hmis)

After creating, suggest using /publish-wiki to commit and push to the GitHub Wiki.

write-wiki

Source facts

Install options

Review the source files

More from this repository

More from this repository

Write Wiki Documentation

Arguments

Target Audience

Required Structure

Writing Rules

What NOT to Include

File Location

Write Wiki Documentation

Arguments

Target Audience

Required Structure

Writing Rules

What NOT to Include

File Location