Syntax
Options
Path to the card directory to publish. Defaults to the current directory.
Usage examples
How it works
scoutica publish uses Git to commit and push your card. Its behavior depends on whether the target directory already has a Git repository.
Existing Git repo
If a.git directory is found, the CLI:
- Stages only the canonical card files (see below)
- Creates a commit with the message
Update Scoutica Skill Card — YYYY-MM-DD - Pushes to the current branch on
origin
New repo setup
If no.git directory is found, the CLI walks you through initial setup:
Enter repo details
You are prompted for a GitHub repo name (default:
my-scoutica-card) and your GitHub username.Create the GitHub repo
You are shown a link to
https://github.com/new and asked to create the repo with the name you entered.Files that are staged
To prevent accidental commits of raw documents or secrets,publish stages only these canonical card files:
| File / Directory | Staged |
|---|---|
profile.json | Yes |
rules.yaml | Yes |
evidence.json | Yes |
SKILL.md | Yes |
scoutica.json | Yes |
rules/ directory | Yes |
| All other files | Never staged |
Expected output
Prerequisites
- Git must be installed and available in
PATH. The CLI aborts if Git is not found. - The
originremote must be configured and point to your GitHub repository. - You must have push access to the repository.