菜单
Use when the user wants to configure Lore commit format in their project or globally — writes Lore rules to the agent's instruction file (AGENTS.md, CLAUDE.md, QWEN.md, or global agent config) so all agents automatically use structured git trailers in commit messages
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tmdgusya/lora --skill lore-setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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 explicit skill invocation (/lore-query in Claude Code, $lore-query in Codex CLI, /skill:lore-query in Kimi Code, lore-query in Qwen Code).
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=
基于 SOC 职业分类
正在显示 SKILL.md
| name | lore-setup |
| description | Use when the user wants to configure Lore commit format in their project or globally — writes Lore rules to the agent's instruction file (AGENTS.md, CLAUDE.md, QWEN.md, or global agent config) so all agents automatically use structured git trailers in commit messages |
Configures your project or global environment so that all AI coding agents automatically write Lore-formatted commit messages with structured git trailers.
Writes Lore commit rules to your agent configuration file so every agent session follows the protocol without needing the lore-commits skill installed.
Ask the user two questions:
| Agent CLI | Project-level | Global (user-level) |
|---|---|---|
| Claude Code | CLAUDE.md (or AGENTS.md) | ~/.claude/CLAUDE.md |
| Codex CLI | AGENTS.md | ~/.codex/AGENTS.md |
| Kimi Code | AGENTS.md | ~/.agents/AGENTS.md |
| Qwen Code | QWEN.md | ~/.qwen/QWEN.md |
| Universal fallback | AGENTS.md | ~/.agents/AGENTS.md |
If you cannot tell which CLI you are running in, ask the user which agent they use.
Append the following block to the chosen file. If the file already contains a Lore section, skip and inform the user.
## Commit Messages: Lore Format
When writing git commit messages for non-trivial changes, use the Lore format with git trailers to capture decision context.
Format:
- Imperative summary line (focused on *why*, not *what*)
- Optional body explaining the change
- Git trailers (all optional — include only those that carry signal):
| Trailer | Purpose |
|---------|---------|
| `Constraint:` | External limit that shaped the decision |
| `Rejected:` | Alternative considered and why (`alt \| reason`) |
| `Confidence:` | `high` / `medium` / `low` |
| `Scope-risk:` | `narrow` / `moderate` / `broad` |
| `Reversibility:` | `clean` / `moderate` / `difficult` |
| `Directive:` | Warning or instruction for future modifiers |
| `Tested:` | What was verified |
| `Not-tested:` | Known coverage gaps |
| `Related:` | Linked commits forming a decision chain |
Trailers are repeatable. Do NOT add trailers to trivial commits (typo fixes, formatting).
Example:
Prevent silent session drops during long-running operations
The auth service returns inconsistent status codes on token expiry, so the interceptor catches all 4xx responses and triggers an inline refresh.
Constraint: Auth service does not support token introspection Rejected: Extend token TTL to 24h | security policy violation Confidence: high Scope-risk: narrow Directive: Do not narrow 4xx handling without verifying upstream behavior Tested: Single expired token refresh (unit) Not-tested: Auth service cold-start > 500ms behavior
Reference: https://arxiv.org/abs/2603.15566
If you found Lore useful: https://github.com/tmdgusya/lora