ci: 加入三組 GitHub Actions（SKILL 驗證 / Markdown 檢查 / Release Drafter） - #1
Merged
Merged
Conversation
…lease drafting - validate-skills: parse SKILL.md frontmatter and check name/description fields, ensuring `name` matches its folder - markdown-check: markdownlint-cli2 + lychee link checker (lenient config, link failures non-blocking initially) - release-drafter: auto-draft release notes grouped by skill/bug/docs labels
…pushes - markdownlint: disable MD022/MD031/MD032 (blank-line style around headings, fences, lists) so existing SKILL.md prose is not blocked. Real defects (broken refs, duplicate ids, etc.) are still caught. - release-drafter: drop pull_request trigger. The action reads its config from the default branch, so PRs that introduce the config will fail spuriously. Drafts now update on push to main only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
為 SlimStack 加上三條 CI 工作流，全部以「文件型 repo」的需求為主：
validate-skills.yml— PR 與 push 到 main 時，跑scripts/validate_skills.py：SKILL.md，視為 skillname/descriptionname必須跟資料夾名一致（root SKILL.md 例外，因為它是 router）markdown-check.yml— markdownlint + lychee link check.markdownlint.jsonc採寬鬆規則，避免一上線就被中文長行 / inline HTML 卡住fail: false，初期僅報告壞連結不擋 PR；確認所有外部連結都正常後可改成true.lycheeignore範例，方便加入會 rate-limit 的網域release-drafter.yml+.github/release-drafter.ymlskill:new/skill:update/bug/docs/chorebreaking→ major、skill:new→ minor、其他 → patchTest plan
validate-skills與markdown-check，兩者都應通過release-drafter應建立第一份 draft release（v0.0.1 或 v0.1.0，依 PR 標籤）skill:new標籤，merge 後 draft 版號應跳到 minorFollow-ups
fail: false改回trueauto-labelerworkflow 依改動的資料夾自動上skill:*標籤