Skip to content

ci: add Tessl skill review workflow (SHA-pinned) - #25

Merged
VGIL77 merged 2 commits into
Bitterbot-AI:mainfrom
rohan-tessl:fix/pin-skill-review-sha
Jul 26, 2026
Merged

ci: add Tessl skill review workflow (SHA-pinned)#25
VGIL77 merged 2 commits into
Bitterbot-AI:mainfrom
rohan-tessl:fix/pin-skill-review-sha

Conversation

@rohan-tessl

Copy link
Copy Markdown
Contributor

Hey @VGIL77 👋

Following up on the feedback from #13 — this is a standalone PR with just the Tessl Skill Review workflow, pinned to a specific SHA as requested.

What's included

.github/workflows/skill-review.yml — runs tessl skill review on PRs that touch SKILL.md files and posts scores as a PR comment.

Pinned to SHA: tesslio/skill-review@22e928dd837202b2b1d1397e0114c92e0fae5ead (not @main)

What this gives you

  • 🔍 Automatic tessl skill review on every PR touching SKILL.md
  • 💬 One updated PR comment with scores and feedback
  • 🔓 No extra accounts — only GITHUB_TOKEN is used
  • ✅ Non-blocking by default — feedback-only, no red CI
  • 🔒 SHA-pinned for supply-chain safety

No skill changes bundled — just the workflow.


Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch — just addressing the specific ask from last time.

Thanks in advance 🙏

Add .github/workflows/skill-review.yml that runs `tessl skill review`
on PRs touching SKILL.md files and posts scores as a PR comment.

Action is pinned to SHA 22e928dd837202b2b1d1397e0114c92e0fae5ead
(not @main) for supply-chain safety.

- No Tessl login or API token needed — only GITHUB_TOKEN
- Non-blocking by default (feedback-only, no red CI)
- One updated PR comment per run
@ivantezar123-sketch

Copy link
Copy Markdown

@rohan-tessl Thanks for the PR! 👍

Looking good. I'll review it shortly.

@maitymistiranu-star

maitymistiranu-star commented May 22, 2026 via email

Copy link
Copy Markdown

@VGIL77
VGIL77 merged commit 0d136b1 into Bitterbot-AI:main Jul 26, 2026
2 checks passed
@VGIL77

VGIL77 commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Merged — thanks for doing exactly what was asked. Note for future readers: on fork PRs the GITHUB_TOKEN is read-only, so the review comment will only appear for same-repo branches until the action supports a fork-safe pattern.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants