Repository navigation
chore: standard CI workflows, LICENSE, and skill-schema compliance - #5
Merged
Merged
Conversation
N4M3Z
force-pushed
the
forge-obsidian-ci
branch
2 times, most recently
from
June 17, 2026 02:22
0b9cd87 to
0de86d8
Compare
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
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.
Problem
The repo had no CI. The quality gate (
forge validate+ cargo hooks) also flags pre-existing gaps: a missing LICENSE, skills violating the skill schema (missingversion, headings deeper than depth 3, an h1→h3 skip), and Rust formatting drift in theobsidian-basecrate.Approach
quality.yamlandrelease.yaml— the standard module workflows;qualityis the status check the branch ruleset requires.version: 0.1.0on ValidateVault.cargo fmton the crate sources.Test plan
qualitypasses on this PR