Skip to content

ci: add skill-review GitHub Action for automated skill review on PRs - #2

Open
yogesh-tessl wants to merge 1 commit into
ez-lbz:masterfrom
yogesh-tessl:ci/skill-review-action
Open

ci: add skill-review GitHub Action for automated skill review on PRs#2
yogesh-tessl wants to merge 1 commit into
ez-lbz:masterfrom
yogesh-tessl:ci/skill-review-action

Conversation

@yogesh-tessl

Copy link
Copy Markdown
Contributor

Hey @ez-lbz 👋

Thanks for merging #1. The description score jump (50% → 100%) looks solid in production now.

Since you don't have any CI set up yet, I thought it'd be worth adding a lightweight quality gate for future SKILL.md changes. This wires up the same tessl skill review tool from #1 as a GitHub Action.

What this adds

A single workflow file: .github/workflows/skill-review.yml

It runs tessl skill review whenever a PR touches **/SKILL.md and posts a score card as a PR comment. No secrets to configure. Works out of the box with the default GITHUB_TOKEN.

Permissions & trust

The workflow requests two permissions:

Permission Why Scope
contents: read Checkout the PR branch to read SKILL.md files Read-only
pull-requests: write Post the score card as a PR comment Write, scoped to the triggering PR only

The action is pinned to a specific commit SHA (tesslio/skill-review@22e928d...), not a mutable tag. so what you review now is exactly what runs in CI. No silent updates.

If you'd rather avoid the write permission entirely, the action can also run in check-only mode (exit code 1 on score regression, no comment posted), happy to switch to that if you prefer.

How it fits

This repo currently has no CI. This would be the first workflow, scoped narrowly to skill file changes only. It won't trigger on any other file types.

Workflow Trigger Purpose
skill-review.yml (new) PR touching **/SKILL.md Automated skill quality gate

Same disclosure as #1. I work at @tesslio. This is the same tool that generated the score card in #1, just wired up to run automatically.

Thanks 🙏

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.

1 participant