obsidian-community-check

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Obsidian Community Check

## Core Rules

- Use the real Obsidian Community account page with the user's existing authenticated browser session. Do not invent a public API or CLI for the hosted scan.
- Treat this hosted submission as distinct from the repo-local source scan in the `AGENTS.md` Local Validation Gate. Neither replaces the other.
- Submit only a ref whose intended local commit is proven reachable and identical on the remote. Stop on every SHA mismatch.
- If the user explicitly asked to trigger the hosted check, that authorizes this specific submission. Still obey any browser action-time confirmation.

## Choose The Check

- `preview`: scan the requested remote branch, tag or commit before publication.
  Follow the preview preflight and browser workflow below.
- `release`: discover and check an already-published stable version. Follow
  [Stable Release Recognition](#stable-release-recognition). A completed
  `Preview` is not official release recognition, even if its ref is a tag.

The stable release workflow uses only `release` mode after GitHub publication.
Do not add a mandatory or optional `preview` to stable preparation, publication
or recovery. Preview remains available for a separately requested source scan.

The project review form is:

```text
https://community.obsidian.md/account/plugins/personal-assistant/review-branch
```

## Preview Preflight

Run from the `personal-assistant` repo root.

1. Confirm repository state and choose the requested ref. Default to `master` only when the user supplied no branch, tag, or commit:

```bash
git status --short --branch
git rev-parse --show-toplevel
TARGET_REF=master
INTENDED_SHA="$(git rev-parse --verify "${TARGET_REF}^{commit}")"
printf 'target=%s\nintended=%s\n' "$TARGET_REF" "$INTENDED_SHA"
```

Stop if the ref cannot resolve locally. Report uncommitted changes because they are not part of any hosted scan.

2. Resolve the remote-scannable SHA by ref type.

For a local branch:

```bash
REMOTE_SCAN_SHA="$(git ls-remote --exit-code --heads origin "$TARGET_REF" | awk 'NR==1 {print $1}')"
```

For a tag, prefer the peeled target of an annotated tag and fall back to the lightweight tag target:

```bash
REMOTE_SCAN_SHA="$(git ls-remote --tags origin "refs/tags/$TARGET_REF^{}" | awk 'NR==1 {print $1}')"
if [ -z "$REMOTE_SCAN_SHA" ]; then
  REMOTE_SCAN_SHA="$(git ls-remote --exit-code --tags origin "refs/tags/$TARGET_REF" | awk 'NR==1 {print $1}')"
fi
```

For a raw commit SHA, refresh remote-tracking reachability and require at least one fetched remote branch to contain it:

```bash
git fetch --prune --tags origin
REMOTE_CONTAINERS="$(git branch -r --contains "$INTENDED_SHA" | sed 's/^[*[:space:]]*//')"
if [ -z "$REMOTE_CONTAINERS" ]; then
  printf 'STOP commit is not reachable from a fetched remote branch: %s\n' "$INTENDED_SHA"
  exit 1
fi
printf '%s\n' "$REMOTE_CONTAINERS"
REMOTE_SCAN_SHA="$INTENDED_SHA"
```

If network or sandbox policy blocks `ls-remote`/`fetch`, request the needed approval or report `BLOCKED`; do not submit from stale assumptions. For a raw SHA, stop unless the refreshed remote-branch output proves reachability. A local-only tag is not proof.

3. Require exact equality before opening the form:

```bash
if [ -z "$REMOTE_SCAN_SHA" ] || [ "$INTENDED_SHA" != "$REMOTE_SCAN_SHA" ]; then
  printf 'STOP intended=%s remote=%s\n' "$INTENDED_SHA" "${REMOTE_SCAN_SHA:-missing}"
  exit 1
fi
printf 'SCAN_READY ref=%s sha=%s\n' "$TARGET_REF" "$INTENDED_SHA"
```

Never push automatically. If a branch/tag is absent, ahead, divergent, or otherwise mismatched, stop and tell the user exactly what must be pushed or corrected.

4. Avoid duplicates. Before submitting, inspect the Reviews list for an existing `Pending` entry with the same ref and exact commit. Reuse it unless the user explicitly asks to resubmit.

## Preview Browser Workflow

Discover the browser tools available in this session and use one that can access
the user's existing `community.obsidian.md` login, respecting any browser the user
specified. Do not require or install a legacy skill by name. Tool availability
does not replace the visible page and commit evidence below.

1. Open the review form.
2. Verify the logged-in page shows:
   - Heading `Preview a branch scan`.
   - Textbox `Branch, tag, or commit SHA`.
   - Button `Run preview scan`.
3. Fill the verified `TARGET_REF` exactly.
4. Click `Run preview scan` only after `SCAN_READY` evidence exists.
5. Confirm navigation to:

```text
https://community.obsidian.md/account/plugins/personal-assistant
```

6. Find the newest matching Preview row and verify all three fields:
   - `Ref: <TARGET_REF>`.
   - `Commit: <INTENDED_SHA prefix>`.
   - Status `Pending`, `Completed`, or `Failed`.

Treat any page commit that is not an exact prefix of `INTENDED_SHA` as `FAIL: wrong commit scanned`. Stop and do not claim completion.

If no available browser tool can access the authenticated page, or the page is
logged out, blocked by browser security, or shows CAPTCHA/account prompts, stop
and report `BLOCKED`. Do not inspect cookies, passwords, profiles, local storage,

From edonyzpc/personal-assistant, AGPL-3.0.

More from edonyzpc/personal-assistant