Skip to content

chore(docs): sync skills - #62

Merged
tempo-github-sts[bot] merged 1 commit into
mainfrom
automation/sync-skills/docs
Oct 20, 2026
Merged

tempo-github-sts[bot] merged 1 commit into
mainfrom
automation/sync-skills/docs

Conversation

@tempo-github-sts

Copy link
Copy Markdown
Contributor

Generated from skills.json by .github/workflows/sync-skills.yml. Edit the source, not these copies.

Skill Source Change
docs tempoxyz/docs/public/SKILL.md 94d33b6b → 75327186

@tempo-github-sts
tempo-github-sts Bot enabled auto-merge (squash) October 20, 2026 04:07
@tempo-github-sts
tempo-github-sts Bot merged commit e0c5dfc into main Oct 20, 2026
6 checks passed
@tempo-github-sts
tempo-github-sts Bot deleted the automation/sync-skills/docs branch October 20, 2026 04:08

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a routine automated skill sync with a patch version bump.

What was reviewed:

  • The docs version moves from 0.1.3 to 0.1.4 in all 12 places it appears: manifest.config.ts, the four generated plugin manifests, the registry server.json and the six golden fixtures. No 0.1.3 is left anywhere in the repo.
  • The only content change in SKILL.md is one paragraph pointing readers to the partner integration guides. The link uses the same canonical tempo.xyz/developers docs location as the other links in the file.
  • I couldn't recompute the lock digest locally. The external skill-sync action computes it, and neither the old nor the new digest equals a plain sha256 of SKILL.md, so the scheme is unchanged. The lock's commit matches the commit range in the PR description.
Extended reasoning...

The change bumps the docs plugin version across its manifests, registry entry and golden fixtures. It also re-syncs the vendored SKILL.md (one new documentation paragraph) and updates the upstream commit and digest in skills.lock.json. It touches no executable code and no auth, crypto or other sensitive surface. Every version occurrence is consistent, the repo has no CODEOWNERS file, and the PR timeline shows no reviewer objections. The diff is small and mechanical, and the repo's sync-skills workflow produced it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants