opencode-skills-collection 1.0.147 → 1.0.149

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-04-05T07:09:21.096Z",
+  "updatedAt": "2026-04-05T09:40:36.395Z",
   "entries": [
     "00-andruia-consultant",
     "007",

package/bundled-skills/docs/contributors/skill-anatomy.md

@@ -47,6 +47,8 @@ name: my-skill-name
 description: "Brief description of what this skill does"
 risk: safe
 source: community
+source_repo: owner/repo
+source_type: community
 ---
 ```
 
@@ -81,6 +83,18 @@ source: community
 - **Examples:** `source: community`, `source: "https://example.com/original"`
 - **Use `"self"`** if you are the original author
 
+#### `source_repo`
+- **What it is:** Canonical GitHub repository identifier for external upstream material
+- **Format:** `OWNER/REPO`
+- **Example:** `source_repo: Dimillian/Skills`
+- **When required:** Use it when the skill adapts or imports material from an external GitHub repository
+
+#### `source_type`
+- **What it is:** Which README credits bucket the upstream repo belongs to
+- **Values:** `official` | `community` | `self`
+- **Examples:** `source_type: official`, `source_type: community`
+- **Rule:** `self` means no external README repo credit is required
+
 ### Optional Fields
 
 Some skills include additional metadata:
@@ -91,12 +105,22 @@ name: my-skill-name
 description: "Brief description"
 risk: safe
 source: community
+source_repo: owner/repo
+source_type: community
 author: "your-name-or-handle"
 tags: ["react", "typescript", "testing"]
 tools: [claude, cursor, gemini]
 ---
 ```
 
+### Source-credit contract
+
+- External GitHub-derived skills should declare both `source_repo` and `source_type`.
+- `source_type: official` means the repo must appear in `README.md` under `### Official Sources`.
+- `source_type: community` means the repo must appear in `README.md` under `### Community Contributors`.
+- `source: self` plus `source_type: self` is the correct shape for original repository content.
+- PR CI checks README credit coverage for changed skills, so missing or misbucketed repo credits will block the PR once `source_repo` is declared.
+
 ---
 
 ## Part 2: Content

package/bundled-skills/docs/contributors/skill-template.md

@@ -4,6 +4,8 @@ description: "Brief one-sentence description of what this skill does (under 200
 category: your-category
 risk: safe
 source: community
+source_repo: owner/repo
+source_type: community
 date_added: "YYYY-MM-DD"
 author: your-name-or-handle
 tags: [tag-one, tag-two]
@@ -17,6 +19,13 @@ tools: [claude, cursor, gemini]
 A brief explanation of what this skill does and why it exists.
 2-4 sentences is perfect.
 
+If this skill adapts material from an external GitHub repository, declare both:
+
+- `source_repo: owner/repo`
+- `source_type: official` or `source_type: community`
+
+Use `source: self` and `source_type: self` when the skill is original to this repository and does not require README external-source credit.
+
 ## When to Use This Skill
 
 - Use when you need to [scenario 1]

package/bundled-skills/docs/maintainers/merge-batch.md

@@ -0,0 +1,55 @@
+# Merge Batch
+
+`merge:batch` is the maintainer shortcut for merging multiple PRs in order while keeping the GitHub-only squash rule and the post-merge contributor sync.
+
+## Prerequisites
+
+- Start from a clean `main`.
+- Make sure [`.github/MAINTENANCE.md`](/Users/nicco/Projects/antigravity-awesome-skills/.github/MAINTENANCE.md) is the governing policy.
+- Have `gh` authenticated with maintainer permissions.
+- Use this only for PRs that are already expected to merge; conflicting PRs still need the manual conflict playbook.
+
+## Basic Usage
+
+```bash
+npm run merge:batch -- --prs 450,449,446,451
+```
+
+Add `--poll-seconds <n>` if you want a slower or faster status loop while checks settle.
+
+## Happy Path
+
+`merge:batch` will:
+
+- refresh the PR body when the Quality Bar checklist is missing
+- close and reopen the PR if stale metadata needs a fresh `pull_request` event
+- approve fork runs waiting on `action_required`
+- wait for the fresh required checks on the current head SHA
+- merge with GitHub squash merge
+- pull `main`, run `sync:contributors`, and push a README-only follow-up if needed
+
+## What It Automates
+
+- PR body normalization against the repository template
+- stale PR metadata refresh
+- required-check polling for the current PR head
+- the post-merge contributor sync step
+- the retry loop for `Base branch was modified`
+
+## What It Does Not Automate
+
+- conflict resolution on the PR branch
+- manual judgment for risky skill changes
+- README community-source audits when the source metadata is ambiguous
+- fork-only edge cases that require contributor coordination outside GitHub permissions
+
+## When To Stop
+
+Stop and switch to the manual playbook when:
+
+- the PR is `CONFLICTING`
+- `merge:batch` reports a check failure that needs source changes, not maintainer automation
+- the PR needs a manual README credits decision
+- fork approval or branch permissions are missing
+
+In those cases, follow [Merging Pull Requests](/Users/nicco/Projects/antigravity-awesome-skills/docs/maintainers/merging-prs.md) and the relevant sections in [MAINTENANCE.md](/Users/nicco/Projects/antigravity-awesome-skills/.github/MAINTENANCE.md).

package/bundled-skills/docs/maintainers/merging-prs.md

@@ -9,6 +9,7 @@
 - Do **not** integrate a PR by squashing locally, pushing to `main`, and then closing the PR. That would show "Closed" and the contributor would not get proper credit.
 - Before merging, require the normal PR checks from [`.github/workflows/ci.yml`](../../.github/workflows/ci.yml) to be green. If the PR touches `SKILL.md`, also require the separate [`skill-review` workflow](../../.github/workflows/skill-review.yml) to pass.
 - For PRs that touch `SKILL.md` or risky guidance, require a real manual logic review in addition to the automated checks. Confirm the instructions, failure modes, and `risk:` label make sense before merging.
+- For ordered multi-PR maintainer batches, use [Merge Batch](merge-batch.md) as the operational shortcut and keep this document as the policy reference.
 
 ## If the PR has merge conflicts
 
@@ -77,5 +78,6 @@ Only if merging via GitHub is not possible (e.g. contributor unreachable and you
 
 ## References
 
+- [Merge Batch](merge-batch.md)
 - [GitHub: Creating a commit with multiple authors](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)
 - [GitHub: Merging a PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "1.0.147",
+  "version": "1.0.149",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",