docs(skills): add graphile-postgis skill for @spatialRelation + RelationSpatial#999
Merged
pyramation merged 2 commits intomainfrom Apr 18, 2026
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:
|
…ms with user-facing ones
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
Adds a new
.agents/skills/graphile-postgis/SKILL.mdso future Devin sessions (particularly agentic-DB sessions, which were the original motivator for the PostGIS work) reach for the right primitive when a task involves spatial queries.The skill covers:
@spatialRelation+ the 8-operator reference table (including thest_dwithinparametric case).RelationSpatialnode (one-direction-per-tag, idempotent, metadata-only).where:usage —some/every/nonesemantics, parametricdistance:, and composition withand/or/not.distance: 0corner case).@spatialRelationSkipIndexCheckescape hatch.column reference "name" is ambiguous, bare vsmetaschema-modules:-prefixed pgpm.plan refs, smart-tag clobber,some: {}semantics, SRID vs meters).orderBy).Also adds a one-line cross-link to the new skill from
constructive-monorepo-setup/SKILL.mdunder the "Graphile Plugin Development" section so it's discoverable from the monorepo entry-point skill.No code changes. Plugin README already contains the full reference (from #994) — this skill is deliberately a shorter, task-oriented summary that points at the README for deep details.
Review & Testing Checklist for Human
graphile/graphile-postgis/README.mdandgraphql/node-type-registry/src/relation/relation-spatial.tsto confirm the skill doesn't drift from the source of truth.../../../graphile/graphile-postgis/...and../../../graphql/node-type-registry/...(three levels up from.agents/skills/graphile-postgis/). Click through once to verify GitHub renders them.Notes
constructive-io/constructive-db#844(parameter ambiguity) and the pgpm cross-module reference issue in the same PR, so they'll appear verbatim in future sessions.Link to Devin session: https://app.devin.ai/sessions/c5eeee65a3c546c4ac6753bb05fa03e0
Requested by: @pyramation