S

Snoboard CLI

Reviews snoboard commands that write initiative.md or fetch from origin. validate, status, and next-number without --fetch only read and are

Reviews snoboard commands that write initiative.md or fetch from origin. validate, status, and next-number without --fetch only read and are not matched. fix --dry-run, --help, and --version exit without writing. Upstream CLI 0.1.0.

command.snoboard · v1.0.0 · Other extensions

By Community contributorExternal · opt-inCommand coverage
Try this coverage Install GuardView exact source Documentation Claim this coverage
0
Protection rules
3
Permission checks
3
Mapped commands
3

Overview

What this coverage does

Reviews snoboard commands that write initiative.md or fetch from origin. validate, status, and next-number without --fetch only read and are not matched. fix --dry-run, --help, and --version exit without writing. Upstream CLI 0.1.0.

Key facts

Catalog ID
command.snoboard
Version
v1.0.0
Kind
Command coverage
Category
Other extensions
Protection rules
3
Permission checks
3
Mapped commands
3
Maintainer
Community contributor(community, provenance recorded)
Source commit
d2db0e9
Protection model
External · opt-in
External · opt-in

External coverage. It must be enabled through Guard controls; this page does not activate it.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

3 operations · 3 reviewed by default These are catalog defaults, not your workspace policy.

3 operations3 reviewed
Default floor

Showing 3 of 3 operations

  • Reviewed Guard intercepts the command for review before it runs.High
    • snoboard fix
    Normalise initiative files
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `snoboard fix`, which rewrites initiative frontmatter. `--dry-run` writes nothing. `--help` and `--version` exit before any write.
    Documented safe variants
    Preview normalisations without writingfix command helpfix command versionskip this operation when they are the documented preview or help form.
    Permission ID
    command.snoboard.permission.fix
  • Reviewed Guard intercepts the command for review before it runs.High
    • snoboard new acme search --title "Search"
    Create an initiative file
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `snoboard new`, which writes a new initiative.md. `--help` and `--version` exit before any write.
    Documented safe variants
    new command helpnew command versionskip this operation when they are the documented preview or help form.
    Permission ID
    command.snoboard.permission.new
  • Reviewed Guard intercepts the command for review before it runs.Medium
    • snoboard next-number acme --fetch
    Fetch origin before numbering
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `snoboard next-number --fetch`, which runs git fetch against origin. The same command without `--fetch` is not matched.
    Documented safe variants
    next-number helpnext-number versionskip this operation when they are the documented preview or help form.
    Permission ID
    command.snoboard.permission.fetch

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.snoboard
Guard enforcement ID
command.snoboard
Source path
contributions/extensions/command.snoboard.json
Contribution digest
sha256…52af7b

Action classes

snoboard initiative writesnoboard origin fetch

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

Reviews snoboard commands that write initiative.md or fetch from origin. validate, status, and next-number without --fetch only read and are not matched. fix --dry-run, --help, and --version exit without writing. Upstream CLI 0.1.0. The listing declares 3 rules and 3 permission checks. 3 operations · 3 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

3 operations · 3 reviewed by default. Examples: snoboard fix (reviewed by default); snoboard new acme search --title "Search" (reviewed by default); snoboard next-number acme --fetch (reviewed by default). These are catalog defaults, not your workspace policy.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.snoboard in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 3 rules and 3 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.