grain

Plugin grain from marketplace grain-marketplace in krzysztofdudek/Grain. Commands read from the repo's manifest — 8 days ago.

Skills (1)

• grain

  Ask the repository about its own conventions BEFORE writing code, through the grain MCP tools. Use whenever you are about to create a source file, add a class/function/handler/command/component/test, are unsure where something belongs, or want to know how a kind of change has been done here before —

Slash commands (23)

• /grain:advise

  What this repository's own history and imports say about the architecture graph it ALREADY has — places a finer cut beats, rules the graph could take on, and (as data, not advice) places that change together with nothing connecting them

• /grain:check

  Ask the repo how a file — or your whole uncommitted change — sits against the local norm (deviations with evidence and exemplars)

• /grain:cochange

  Which parts of a set of files or graph nodes change together more often than chance, and how well a proposed cut of them into parts follows the seams the history shows

• /grain:completeness

  Ask the repo which other files historically change together with the given file(s) — co-change, above a confidence floor

• /grain:decide

  Record a maintainer decision — steer (promote a pattern), boundary (forbid an import direction), or waive (excuse one scope) — or list/withdraw one

• /grain:explain

  Show the full local-to-global convention lattice around one file (no acceptance cut)

• /grain:export

  Dump the whole convention model as JSON (every convention with all its sites, anchors, trends, groups, markers, co-change) for pipelines and audits

• /grain:how

  Ask the repo how a change like <intent> has actually been made here before — real past commits, not a guess

• /grain:map

  A structural overview of the repo — dependency layers, top concepts, certified change shapes, decisions in force

• /grain:measure

  What the work between two commits did to a territory — its files, its imports inside and across its edge, the undeclared dependencies between nodes, and how often the range crossed its edge

• /grain:obligation

  What a NEW file under this path has historically required — obligations mined from git status alone, before the file is written

• /grain:oracle

  Keep the difference between the graph grain proposed and the graph you accepted, and score the proposal against it — precision and recall on the same measures grain is held to on hand-written graphs

• /grain:propose

  Mine a PROPOSED Yggdrasil `.yggdrasil/` architecture graph for this repository — nodes, relations and rules with evidence — into a staging directory for a human to accept with `yg adopt`

• /grain:refresh

  Rebuild the grain index for this repo now (queries auto-refresh; use after a history rewrite)

• /grain:report

  grain report — the repository's top conventions with evidence and trends

• /grain:review

  Alias of `check` with no file argument — one aggregated report over your whole uncommitted change

• /grain:rules

  Generate a standalone Markdown document of this repo's established conventions, for a reader with no terminal and no grain plugin

• /grain:selftest

  Plant synthetic deviations into conforming exemplars and report how many this repo's own model catches (or evaluate `how`, `where` or extraction itself against a naive baseline/oracle)

• /grain:spectrum

  Alias of `explain` under its original name — same command, same output

• /grain:status

  grain index status — freshness, size, health of the convention model for this repo

• /grain:steer

  Alias of `decide steer` under its original name — record a maintainer decision that promotes a pattern repo-wide

• /grain:what

  Ask the repo what <words> already IS here — declarations, values, spread, siblings, commit mentions, fan-in

• /grain:where

  Ask the repo where things like <intent> live, what is expected there, and which exemplar to copy

MCP servers (1)

• grain

  runs: node -e const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.ex

Hooks (7)

• SessionStart

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• PostToolUse

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• PostToolUse

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• PreToolUse

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• PreToolUse

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• PreToolUse

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

• UserPromptSubmit

  node -e "const f=process.argv[1];if(!require('fs').existsSync(f)){console.error('grain: '+f+' is not reachable from this environment (a host path inside a container?), so grain did not run');process.e

Similar plugins