semantic-praxis
Official@semantic-praxis
Semantic Praxis: tools for the ongoing work of modeling shared meaning.
Agent Skills by semantic-praxis
Showing 12 vetted skills indexed across 1 GitHub repositories.
semantic-praxisassertion-audit
Audits test suites for assertions that pin limitations or pass for the wrong reason.
semantic-praxisdistill
Rebuilds bloated LLM-drafted documents from their inventoried claims and reports every dropped claim.
semantic-praxisrelease
Automates version bumping, tagging, and GitHub release creation for the barwise monorepo.
semantic-praxisgym-coach
Diagnoses recurring ORM modeling failures from gym session logs and recommends exercises and readings.
semantic-praxisarticulation
Diagnose and fix clarity barriers in prose, code, data models, and requirements.
semantic-praxisduplication-audit
Detect and classify must-agree code copies that can silently diverge across a codebase.
semantic-praxisbarwise-modeling
Build, validate, verbalize, and export ORM 2 conceptual models in .orm.yaml files.
semantic-praxissteward
Drives barwise pull requests to green by resolving CI failures, review events, and merge conflicts.
semantic-praxisspec-writer
Writes reviewable design specs for barwise changes using the house template and pre-push gate.
semantic-praxissession-review
Extract process findings from work sessions into PR review sections.
semantic-praxispr-review
Reviews barwise pull requests and produces a verified merge recommendation with ranked findings.
semantic-praxispr-creation
Writes pull request titles and bodies that transmit the author's model of a change.
Frequently Asked Questions About semantic-praxis
FAQPage SchemaWhat tasks can I accomplish with semantic-praxis skills?▼
You can build and validate ORM 2 conceptual models with the barwise toolkit, write design specs before code, create and review pull requests, cut monorepo releases with correct version-bump sequencing, audit tests that pin wrong behavior, detect drifting code duplication, distill bloated drafts, and coach ORM learners from their modeling-gym history.
Who are these skills designed for?▼
They target contributors and maintainers of the barwise monorepo, engineers practicing spec-before-code development, reviewers judging PR mergeability, and learners improving at Object-Role Modeling through the modeling gym's session records and reductive-bias catalog.
How do the barwise modeling skills run in practice?▼
The barwise-modeling skill operates over .orm.yaml files through the barwise CLI, MCP server, or VS Code extension, covering building, validating, verbalizing, diagramming, diffing, and exporting conceptual models. The gym-coach skill reads session records from $XDG_STATE_HOME/barwise/ to recommend exercises.
What conventions govern pull requests and releases?▼
The project enforces spec-before-code: changes start as docs/specs/*.spec.md files. PR skills transmit the author's model of the change, the steward drives CI to green, and the release skill handles the single monorepo version bump, tagging, and GitHub release while avoiding workspace dependency and SERVER_VERSION sync pitfalls.
What prerequisites do these skills assume?▼
Skills assume the barwise repository context: conventions live in CLAUDE.md, AGENTS.md, the PR template, and referenced checklists. Modeling work requires the barwise toolkit installed (CLI, MCP server, or VS Code extension), and gym-coach requires existing modeling-gym session records under $XDG_STATE_HOME/barwise/.