docs(skills): add graphile-meta skill; ignore docs in CI; drop skill zips#1395
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Summary
Three related changes:
1. New
graphile-metaskill (.agents/skills/graphile-meta/SKILL.md)documenting the
_metaschema-introspection plugin (MetaSchemaPlugin/MetaSchemaPresetingraphile-settings). There was no skill for it — theexisting
cli-meta/orm-metaskills cover a different thing (the metaschemaAPI target in constructive-db), not the graphile
_metaquery. Theskill covers the plugin architecture (two schema hooks, build-time cache), the
full
_metashape, the smart-tag→builder→Meta*type contract, a 6-step recipefor adding a new metadata block (written around the in-flight
scopeaddition),and why
_metamatters for codegen.2. CI: ignore docs-only changes.
run-tests.yamlhad abranches:filterbut no
pathsfilter, so every PR tomain/v1ran the full ~38-job suite —including markdown-only ones (this PR's first push triggered all of them). Added
paths-ignoreto both thepushandpull_requesttriggers:Note: GitHub evaluates
paths-ignorefrom the base branch's workflow, so this PRstill runs full CI (it also edits the workflow + deletes files); the skip takes
effect for future docs-only PRs after merge.
3. Removed the committed skill
.zipbundles. The 6 curated skills eachshipped a
.zipnext to their dir. Nothing in the repo references or consumesthem (no build script / workflow / tooling) — they were a one-off manual artifact
from the "add 6 tooling skills" commit. Deleted all 7 (
constructive-cli,constructive-pnpm,constructive-setup,constructive-testing,graphile-search,pgpm, and thegraphile-metaone I'd just added).Docs / CI-config only; no runtime code changes.
Link to Devin session: https://app.devin.ai/sessions/819d1e4face6493393be40f35a48af33
Requested by: @pyramation