// Use when the user wants to query Lore git trailers from commit history — surface constraints, rejected alternatives, directives, test gaps, and other decision context. Triggers on "최근 제약조건 확인", "리젝된 대안 보여줘", "check recent constraints", "show directives", or /lore-query.
Use when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
Use when the user wants to configure Lore commit format in their project or globally — writes Lore rules to AGENTS.md, CLAUDE.md, or global agent config so all agents automatically use structured git trailers in commit messages
| name | lore-query |
| description | Use when the user wants to query Lore git trailers from commit history — surface constraints, rejected alternatives, directives, test gaps, and other decision context. Triggers on "최근 제약조건 확인", "리젝된 대안 보여줘", "check recent constraints", "show directives", or /lore-query. |
Query Lore git trailers from commit history to surface decision context.
/lore-query # Summarize all Lore trailers from recent commits
/lore-query <trailer> # Query specific trailer type
/lore-query <trailer> <path> # Scope to file or directory
Natural language also works: "최근 제약조건 확인해줘", "show me rejected alternatives for src/auth/", etc.
The user may refer to trailers by Korean shortcut, English shortcut, or full trailer name. Map them as follows:
| Shortcut | Trailer |
|---|---|
| 제약조건, constraints | Constraint: |
| 리젝, rejected | Rejected: |
| 디렉티브, directive | Directive: |
| 미테스트, not-tested | Not-tested: |
| 테스트, tested | Tested: |
| 신뢰도, confidence | Confidence: |
| 범위위험, scope-risk | Scope-risk: |
| 가역성, reversibility | Reversibility: |
| 관련, related | Related: |
Any unrecognized name is treated as a custom trailer (query it as-is).
Run this via the Bash tool:
git log -n 20 --all --grep="^TRAILER_NAME:" --format="%h %s%n%b" -- [PATH]
Replace TRAILER_NAME with the mapped trailer name (e.g., Constraint). Omit -- [PATH] if no path was specified.
Then parse the output: for each commit, display the short hash, summary line, and only the matching trailer lines.
Run this via the Bash tool:
git log -n 20 --format="%h %s%n%b"
Scan the output for any lines matching known Lore trailers (Constraint:, Rejected:, Directive:, Confidence:, Scope-risk:, Reversibility:, Tested:, Not-tested:, Related:). Only show commits that contain at least one Lore trailer.
Present results as a compact list. Show the short commit hash and summary, then indent matching trailer lines below:
a1b2c3d Prevent silent session drops
Constraint: Auth service does not support token introspection
Constraint: Must not add latency to non-expired-token paths
f4e5d6c Add rate limiter to external API calls
Constraint: Rate limit 100 req/s on external API
If no Lore trailers are found, say so clearly: "No Lore trailers found in recent commits."
In summary mode, group output by commit (not by trailer type) to preserve decision context.
src/auth/, src/api/handler.ts).