ossappscollective/OSS-DocumentScanner

commit

MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.

feat

Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with `--investigate`. Add `--auto` to run unattended (never asks; build stops at a draft PR). Use anytime you need to build a feature, or to plan one ahead…

branch-check

Ensure you're on a correct working branch off up-to-date main before planning or editing — starting from a GitHub issue when one is in play.

writing-great-skills

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

document

best practices to write good documentation

fix

Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only. Default (`/fix [issue]`) = systematic debugging → fix → PR. `--investigate` = read-only bug triage that posts a structured investigation as a GitHub issue comment…

investigate-contract

Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own.

open-pr

MANDATORY skill for ALL pull requests. Must be used EVERY TIME before creating any pull request. No exceptions.

save-plan-to-github

Post a plan or investigation block as a comment on a GitHub issue. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own. The domain-specific template lives in the calling skill.

understand-project

Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Internal helper invoked by feat / fix (both modes) — not meant to be run on its own.