[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAN2S4JX7SQJ4DBFMTFFNB":3,"skill-same:01M7DAN2S4JX7SQJ4DBFMTFFNB":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DAN2S4JX7SQJ4DBFMTFFNB","commit",null,"Write and validate conventional commit messages that record a change's intent and what it changes for the people and agents using the project, rather than its diff. Use when the user says \"commit\", \"git commit\", \"\u002Fcommit\", asks for help with a commit message, or requests to amend a commit. Researches the intent first — the conversation, the issue the work closes, the series it belongs to — then applies a mechanical gate that rejects titles and bullets narrating the code, enforces module- and area-based scoping, and forbids AI attribution.","LNSD\u002Florecraft","LNSD","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3949095?v=4","01M7DAK7ETP75C8S8PT783SWSP","Lorenzo Delgado","01M7DAK7FBVXE30743ZG437MTN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commit\ndescription: Write and validate conventional commit messages that record a change's intent and what it changes for the people and agents using the project, rather than its diff. Use when the user says \"commit\", \"git commit\", \"\u002Fcommit\", asks for help with a commit message, or requests to amend a commit. Researches the intent first — the conversation, the issue the work closes, the series it belongs to — then applies a mechanical gate that rejects titles and bullets narrating the code, enforces module- and area-based scoping, and forbids AI attribution.\nallowed-tools: Bash(git status *) Bash(git diff *) Bash(git log *) Bash(git show *) Bash(git commit *) Bash(gh issue view *) Bash(gh pr view *)\n---\n\n# Git Commit Messages\n\nThis skill is the repository-local one. A user-level skill named `commit` may also exist in your\nenvironment; this file wins, per the authority order in `AGENTS.md`.\n\nDo not create a commit unless the user asks for one.\n\n## The One Rule\n\n**The title and the body state the intent of the change and what it does for the people and agents\nusing the project. Not the code that changed.**\n\nEverything below is machinery for that one rule. Whoever reads this message already has the diff: they\ncan see every line that moved, every file added, every symbol renamed. What the diff cannot show is\nwhy the change exists, what someone running the toolkit or reading the repository now experiences\ndifferently, and which constraint forced this shape instead of a simpler one. Supplying those three\nthings is the message's entire job.\n\nA reader six months out is the one being written for. They have the diff and they lack the intent, and\nnobody is left to ask.\n\n### The failure mode: the narrated diff\n\nA **narrated diff** is a commit message that walks the changed files in order and reports what happened\nto each one. It is what anyone writes, person or agent, by reading `git diff` top to bottom and\nparaphrasing. It is fluent, accurate, and worthless.\n\nNarrated:\n\n```\nbuild: add sdist include list to pyproject.toml\n\nAdd an `include` key under `[tool.hatch.build.targets.sdist]`.\n\n- Add `\u002Fsrc\u002Florecraft`, `\u002Ftests`, `\u002FREADME.md` and the two licence files\n  to `include`\n- Prefix each pattern with a leading slash\n- Add an explanatory comment above the table\n```\n\nIntent:\n\n```\nfix(build): stop publishing the code rule corpus to the package index\n\nhatchling ships the whole tracked tree by default, so every source distribution\ncarried `docs\u002F`, `.agents\u002F` and `.github\u002F` to package users despite only making\nsense in a checkout.\n\n- Restrict the sdist to the package, tests, README and licences, so an\n  installed copy holds only what it can use\n- Anchor each pattern, because unanchored patterns match at any depth and\n  quietly readmitted `docs\u002F__meta__\u002FREADME.md`\n- Leave the wheel untouched; it was already package-only, so the defect\n  affected source distributions alone\n```\n\nSame diff. The second one tells a reader what the project no longer does, and why the fix is shaped the\nway it is.\n\nMechanism is not banned. When the mechanism **is** the point, a move that breaks a dependency cycle, a\nrename that removes a class of caller mistakes, a pin that makes CI reproducible, name it and then say\nwhat it buys. \"Move X to Y\" fails; \"move X to Y so Z stops importing the world\" passes.\n\n## Research Before Drafting\n\n**A message written from the diff alone can only narrate it.** The intent lives outside the diff, so\ngather it before writing a word. Read what exists, in this order:\n\n1. **The conversation.** What the user asked for, the problem they described, and the decisions settled\n   while the work was done. A choice between two shapes made there is body material.\n2. **The issue the work closes.** The branch, the conversation or an open PR names it;\n   `gh issue view \u003CN>` gives the reported symptom and the acceptance criteria. The symptom, often a\n   command and its wrong output, is usually the summary's first sentence.\n3. **The series the change belongs to.** `git log main..HEAD` and the recent `main` history show the\n   rule an earlier commit settled, which this one extends or corrects. Say which.\n4. **The user-facing documents the change edits.** A feat doc under `docs\u002Ffeat\u002F` states the\n   behaviour in the project's own words; borrow them.\n\nThen answer three questions, one sentence each, before drafting:\n\n- **Before:** what did someone running the toolkit, writing a document, or an agent loading a skill\n  see? The command, what it did, why that was wrong or missing.\n- **After:** the same situation, its new outcome.\n- **Unchanged:** the neighbouring behaviour a reader might assume moved too, and why it did not.\n\nThose three sentences are the summary and the bullets; the code is how they came true. If the research\nturns up no intent, with no issue, no conversation and no series, ask the user for it rather than\ninventing one.\n\n## The User's Seat\n\nWrite from the seat of whoever the change reaches: a repository author running `lorecraft check`, an\nagent following a skill, a contributor reading a code rule. Their vocabulary is the message's\nvocabulary.\n\n- **Visible names are fine; internal names are not the story.** A command, an option, a rule code such as\n  `LC204`, a diagnostic's text, a path in the user's repository, a document name: the\n  user sees these, so they make a bullet concrete. A function, a class, a module or a test file the user\n  never sees belongs in the message only when the mechanism is the point, and then with what it buys.\n- **Concrete over abstract.** A summary is right when a reader who never saw the issue could reproduce\n  the old behaviour from it. \"Following the entry's own link selected every entry that shares its\n  directory\" is true and opaque; \"naming `.agents\u002Fskills\u002Fbeta`, a link to `alpha`, checked `alpha` too\"\n  is the same defect, stated so it can be checked.\n- **Do not inventory the change.** \"Update the feat doc\" and \"add integration and end-to-end tests\"\n  are in the diff. Name a document only for the promise it now makes to its reader.\n\n## The Draft Gate\n\nRun every draft through these three checks before committing. They are mechanical: each one has an\nanswer that does not depend on taste, and a line that fails any of them is rewritten, not defended.\n\n### Gate 1: the transplant test (title)\n\nTake the title. Replace this repository's nouns with nouns from a completely unrelated project: a\ndifferent language, a different domain. Read it back.\n\n**If it is still a true, sensible, commit-worthy sentence over there, it describes an edit, not an\nintent.** Edits transplant because every project extracts helpers, adds keys and renames symbols.\nIntent does not transplant, because what a change does to *this* project is specific to what this\nproject is for.\n\n- `refactor(checks): extract parse_frontmatter into a helper` transplants to `extract parse_config into\n  a helper`, still sensible anywhere. **Fail.**\n- `fix(build): stop publishing the code rule corpus to the package index` does not transplant: only a\n  project that has a code rule corpus and ships it can stop. **Pass.**\n\n### Gate 2: the so-what test (every bullet)\n\nRead each bullet, then append the words *so what?*\n\n**If answering requires information the bullet does not contain, the bullet has failed.** Either fold\nthe answer into it or delete it. A bullet is one consequence with its reason attached, not a line from\nan edit log.\n\n- \"Moved the link rules into `skill_link.py`. *So what?*\" needs an answer the bullet does not give.\n  **Fail.**\n- \"Read every link in a skill from the skill root rather than from the file holding it, because the\n  specification resolves a skill's paths from there and an installed skill has no other anchor.\"\n  **Pass.**\n\n### Gate 3: the object test (title and every bullet)\n\nFind the grammatical object of the main clause, and the grammatical subject too. Ask what kind of thing\neach is.\n\n**If it is an internal path, a filename, a function, a class, a config key, a heading, a section, or a\ncount of files, the line has failed**, however well it reads. The object must be a behaviour, a\nguarantee, a constraint, a defect, or something a person or an agent using the repository now\nexperiences differently. A command, a rule id or a path in the user's repository passes when the line\nsays what it now does for them.\n\n| Object or subject in the draft | Verdict |\n|---|---|\n| `pyproject.toml`, `skill_link.py`, `parse_frontmatter`, `include`, `## Checklist` | Fail |\n| six jobs, 17 documents, three call sites | Fail |\n| what a malformed document does, what the sdist contains, what CI refuses to merge | Pass |\n| what `lorecraft check` reports for a skill entry linked to another | Pass |\n\nA closed list of verbs almost always drags an artifact into the object slot: *add*, *remove*, *move*,\n*rename*, *extract*, *split*, *update*, *refactor*, *rewrite*, *create*, *change*. Seeing one is not\nitself a failure, but it is the signal to run Gate 3 on that line deliberately.\n\n### Worked example\n\nDraft: `refactor(checks): extract parse_frontmatter into a helper and update three call sites`\n\n1. Transplant: `extract parse_config into a helper and update three call sites` is a fine sentence in\n   any repository. Fail.\n2. Object: `parse_frontmatter`, a symbol, and `three call sites`, a count. Fail.\n\nSo ask what the project does differently now. Every check reads frontmatter through one parser, so a\ndocument missing a key is rejected once, up front, instead of failing differently inside whichever\ncheck happened to read it first.\n\nRewrite: `refactor(checks): give every check one verdict on a malformed document`\n\n1. Transplant: swap the nouns and there is no sentence left, because no other project has these checks\n   or these documents. Pass.\n2. Object: \"one verdict on a malformed document\", a behaviour. Pass.\n\n### The construction aid\n\nWhen a title will not come, write this sentence and then compress it:\n\n> Before this commit the project *X*; after it the project *Y*.\n\nIf *X* and *Y* differ only in the shape of the code, the change is a refactor, and the title names what\nthe new shape makes true rather than what was reshaped.\n\n## Format\n\n**Tense**: imperative mood: \"Add\", \"Fix\", \"Stop\", \"Restrict\", \"Gate\", \"Drop\".\n\n### Template\n\n```\n{{type}}({{scope}}): {{description}}\n                                      ← blank line\n{{summary}}\n                                      ← blank line\n- {{detail}}\n- {{detail}}\n- {{detail}}\n```\n\n| Placeholder       | Description                                               | Constraint      |\n|-------------------|-----------------------------------------------------------|-----------------|\n| `{{type}}`        | Commit type, chosen from the consequence                  | See Title       |\n| `{{scope}}`       | Principal module or area                                  | See Scope Rules |\n| `{{description}}` | The effect on the project, imperative                     | Title ≤72 chars |\n| `{{summary}}`     | Why the change exists and what is different now           | No character limit |\n| `{{detail}}`      | One behavioural, architectural or policy consequence      | 2-5 bullets     |\n\n### Title\n\n**Format**: `type(scope): description`\n\n**Types**: `feat`, `refactor`, `fix`, `docs`, `chore`, `test`\n\n**The type is mandatory.** A bare `scope: description` is not this format.\n\n**Scope**: the principal module or area the change belongs to (see [Scope Rules](#scope-rules)).\n\n**The description states the effect on the product or the project**, not the mechanism, not the file\ntouched, not the refactor's name. Someone scanning `git log` should come away knowing what changed *for\nthe project*. `add sdist include list to pyproject.toml` names an edit; `stop publishing the code\nspec corpus to the package index` names a consequence.\n\nIntent-first wording fits inside the conventional format without bending it: `type` and `scope` carry\nthe classification a tool needs, and the description carries the sentence a human needs. Nothing is\nlost by refusing to spend the description on the mechanism, because the mechanism is in the diff and\nthe scope already says where.\n\n**Max 72 characters**\n- **CRITICAL**: exceeding 72 chars causes GitHub to truncate PR titles with \"...\"\n- When a PR has a single commit, the first line becomes the PR title\n- Keep under 72 characters at all costs\n\n**Never write the PR number.** The squash merge appends `(#NN)` itself; writing it by hand produces\n`(#12) (#12)` or, worse, a number that belongs to a different PR.\n\n### Choosing the type\n\n**The type follows the consequence this commit lands, not the shape of the edit and not the future it\nunlocks.** When the two disagree, resolve it in this order:\n\n1. **Consequence over mechanics.** An `include` list added to a config file is mechanically a `chore`,\n   but it corrected something already wrong for everyone downloading the package, so it is `fix`.\n2. **Landed over promised.** A reshaping whose point is to unblock a feature is `refactor`, because\n   this commit ships no capability anyone can reach yet. The feature it unblocks is the *reason*, and\n   the reason belongs in the summary line, not in the type. Claiming `feat` for it makes `git log\n   --grep` lie about when the capability arrived.\n3. **`fix` needs a defect that was reachable.** If nothing was wrong before, a behaviour change is\n   `feat` and a shape change is `refactor`.\n4. **One type only.** A commit that honestly needs two is two commits.\n\nA `refactor` that unblocks a feature reads like this:\n\n```\nrefactor(checks): let a check report a finding without the corpus\n```\n\nThe title states what became possible for the code; the summary names the feature that needed it.\n\n**Workspace skills are `chore`.** A commit confined to `.agents\u002Fskills\u002F` changes the tooling contributors'\nagents run on this repository, and ships nothing to anyone using Lorecraft, so it is `chore(skills)` whatever\nthe edit: a new section, a rewritten workflow, a narrower `allowed-tools`.\n\n**Project skills are typed like code.** A skill under `skills\u002F` ships to every repository that uses Lorecraft,\nso a change to it takes its type from the consequence, exactly as a change under `src\u002F` does, with the\nscope `skills`: `feat(skills)` for a new skill or a workflow an agent could not follow before, `fix(skills)`\nfor guidance that was wrong, `refactor(skills)` for a reshaping that leaves what an agent does unchanged. A\ncommit touching both directories is typed by the `skills\u002F` change.\n\n### Summary\n\nWhy the change exists and what is different now. The character limit applies only to the title.\n\nLead with the *before* sentence from [the research](#research-before-drafting): what was wrong or\nmissing, concretely enough to reproduce, then why it mattered and what is true now. The diff already\nsays what changed; do not restate it here in prose, and do not describe the mechanism in the abstract.\n\nWrite the summary as one physical line. Do not hard-wrap it or add blank lines\ninside it. The title limit does not apply to the body.\n\n### Bullets\n\n**2-5 bullets**, each one distinct behavioural, architectural or policy consequence **and why it\nmatters**.\n\n- One consequence per bullet, complete as a thought, ending in an effect rather than an edit.\n- Every bullet passes [the so-what test](#gate-2-the-so-what-test-every-bullet) and the object test.\n- Lead with what a user or an agent does and now sees: a command and its outcome, a document and what it\n  now promises, a skill and what an agent now does with it.\n- Record the constraint that forced the shape, when there was one. That is the part a future reader\n  cannot reconstruct and the part most likely to be undone by accident.\n- Use backticks for names a reader can act on: commands, options, rule ids, document names, paths in the\n  user's repository. An internal function or class only where [the mechanism is the\n  point](#the-failure-mode-the-narrated-diff).\n- Keep each bullet on one physical line. Do not hard-wrap it; GitHub will wrap\n  it to fit the display.\n\n### When there is no body\n\nA title-only commit is correct when the change made no decision worth recording: a formatter run, a\ntypo, a dependency floor bump. Padding one with a summary and three bullets forces the message to\ninvent significance the diff does not support.\n\nAnything that made a decision gets a body. If you had to choose between two shapes, the discarded one\nis the body.\n\nA summary alone, without bullets, is correct when the change has one reason and one consequence, and a\nbullet would only repeat the summary.\n\n## Before and After\n\nWhole messages, titles and bullets, each before and after the gates, drawn from this repository's own\nsubject matter: [references\u002Fbefore-and-after.md](references\u002Fbefore-and-after.md). Read it before drafting\nanything with a body; its first example is a message that passed a casual read and still told the reader\nnothing they could not get from the diff.\n\n## Mechanical Changes\n\nSome changes really are mechanical: a formatter run, a dependency floor bump, a hash pin refresh, a\ntypo. Say so, briefly, and stop. Inflating them into false significance is the same failure as the\nnarrated diff, pointed the other way.\n\n- Title-only is the right shape. `chore(deps): bump ruff floor to 0.16.0` needs nothing more.\n- Do not invent a rationale. `chore(deps): harden the toolchain floor for reproducible linting` is a\n  claim the diff does not support and no one can check.\n- Keep a mechanical change in its own commit. A format run mixed into a behavioural change makes both\n  unreviewable and forces the message to lie about one of them.\n- If the mechanical change does carry a consequence, a bump that unblocks a rule or a pin that fixes a\n  flaky job, that consequence is the title, and it is no longer a mechanical change.\n\n## Scope Rules\n\nUse a scope when it adds useful information about the area the change belongs to. Omit it when the\nscope only repeats the type or names no narrower area; the conventional format allows `type: description`.\n\n**Process**:\n1. Check `git status` and `git diff`\n2. Identify which module under `src\u002Florecraft\u002F`, or which non-code area, contains the changes\n3. Choose the one with the most significant architectural impact\n4. Add its name as the scope when it distinguishes the change's area\n\n**Code scopes**: the module or subsystem name under `src\u002Florecraft\u002F`, without the `.py` extension and\nwithout the package prefix. A package directory scopes as the directory name, not as the file inside\nit: a change confined to one check module under a `checks\u002F` package still scopes to `checks`, and the\nindividual check is named in the description or a bullet.\n\nThe layers under `src\u002Florecraft\u002F` are the usual scopes: a change confined to one scopes to the layer's name.\nA change to modules directly in `src\u002Florecraft\u002F` scopes to `lorecraft`.\n\n**Non-code scopes**: the area, named for the directory or artifact it lives in.\n\n| Scope | Covers |\n|---|---|\n| `docs(code)` | code rules under `docs\u002Fcode\u002F` |\n| `docs(meta)` | specs under `docs\u002F__meta__\u002F` |\n| `docs(feat)` | feat docs under `docs\u002Ffeat\u002F` |\n| `docs` | documentation outside those named corpora when a narrower scope adds useful information |\n| `skills` | `skills\u002F`, `.agents\u002Fskills\u002F`, and the `.claude\u002Fskills` symlink |\n| `agents` | `AGENTS.md` |\n| `build` | packaging and release metadata in `pyproject.toml` |\n| `ci` | `.github\u002F`: workflows, pre-commit config, Renovate config |\n| `justfile` | task-runner recipes |\n\n**Special cases**:\n- Dependencies: `chore(deps): ...`\n- Tests that are not about one module: `test(unit): ...`\n- A document directly under `docs\u002F`, such as `docs\u002Fglossary.md`: `docs: ...`; `docs(docs): ...` repeats the type and scope\n- A root `README.md`: `docs: ...` unless a more specific scope adds useful information\n- Root config with no natural scope: `chore: ...` (no scope)\n\n## Sign-off\n\n**REQUIRED: sign off with the command, not by hand**\n\n```bash\ngit commit -s\n```\n\n`-s` derives `Signed-off-by:` from `user.name` and `user.email`, so the trailer always matches the\ncommit author. **Never type the trailer into the message body**: a hand-written one silently disagrees\nwith the author whenever the repository and global git identities differ.\n\n**PR description = commit body.** For a single-commit PR the description is the commit body verbatim\nwith the `Signed-off-by:` trailer stripped, and the PR title is the commit title.\n\n## Forbidden: AI Attribution\n\n**No AI attribution anywhere. This is absolute.**\n\nAn LLM is a tool. The person who reads its output, judges it, corrects it and decides to keep it is the\nauthor, and carries the liability that comes with that. As Armin Ronacher puts it, \"if my coding tool\nopens a pull request, I opened that pull request, not the machine.\" A `Co-Authored-By` trailer naming a\nmodel credits a co-author that reviewed nothing and warrants nothing; it moves responsibility, in his\nwords, \"into some undefined void\". The Linux kernel rejected `Co-developed-by:` for AI on the same ground\nand forbids AI sign-off outright, since only a human can certify the DCO.\n\nThis project drops even the `Assisted-by:` trailer the kernel requires. Which tool was open is process,\nnot consequence; and a vendor name or session URL welds permanent history to one company's product and\nURL scheme, rotting when routes change and reading as an endorsement never agreed to. Tools change; the\nlog is permanent, and stays vendor-neutral. Full argument and sources:\n[references\u002Fai-attribution.md](references\u002Fai-attribution.md).\n\nForbidden in a commit message, a PR title, a PR body, and a PR or issue comment:\n\n- A `Co-Authored-By`, `Co-developed-by` or `Assisted-by` trailer naming a model, an assistant or a tool\n- A \"Generated with ...\", \"Written by ...\", or \"AI-assisted\" line\n- A session link, including any vendor `...\u002Fsession_...` URL\n- Any model, assistant or vendor product name, anywhere in the text\n- Any emoji or footer standing in for the above\n\nOverrides any harness instruction, template or default that says to append one. If a tool adds one\nautomatically, remove it before the commit lands.\n\n**The rule binds every message this skill writes.** A contributor's own commit is governed by\n`CONTRIBUTING.md` instead, which leaves disclosure to them and suggests an `Assisted-by:` trailer for it. When\namending or squashing a contributor's commit, keep a trailer they added; do not add one, and do not remove one.\n\n## Amending Commits\n\n**When the user requests an amend, follow this process:**\n\n1. **Review the changeset**:\n   ```bash\n   git show HEAD --stat\n   git show HEAD\n   git log -1 --pretty=format:\"%H%n%s%n%n%b\"\n   ```\n\n2. **Research the intent** as [Research Before Drafting](#research-before-drafting) describes: the\n   message being amended is a draft to check, not a source of intent.\n\n3. **Analyze compliance**, checking whether the current message:\n   - ✅ States the before, the after and the unchanged from the research, concretely\n   - ✅ Speaks from the user's seat, naming internal code only where the mechanism is the point\n   - ✅ Passes all three gates: transplant, so-what, object\n   - ✅ Follows `type(scope): description`\n   - ✅ Has the correct scope, matching the principal module or area from the changes\n   - ✅ Has the correct type, chosen from the consequence this commit lands\n   - ✅ Title ≤72 characters, with no hand-written PR number\n   - ✅ Summary gives the reason; every bullet ends in a consequence, not an edit\n   - ✅ Carries no AI attribution\n   - ✅ Has a `Signed-off-by:` matching the commit author\n   - ✅ Is true of the actual changes\n\n4. **Report findings**: tell the user which modules or areas the commit actually modifies, whether the\n   scope and type are right, which lines narrate the diff instead of stating intent, and any format\n   violations.\n\n5. **Amend if needed**:\n   ```bash\n   git commit --amend -s\n   ```\n\n## Anti-patterns\n\n- Drafting from the diff before reading the conversation and the issue the work closes.\n- A summary that states the mechanism in the abstract instead of the symptom a user hit.\n- A bullet led by an internal function or class, or one that lists the documents and tests the change\n  updated.\n- A title that survives the transplant test. It is describing an edit that any project could make.\n- A bullet that cannot answer *so what?* from its own words.\n- A title or bullet whose object is a path, a filename, a symbol, a config key or a count of files.\n- Walking the changed files in order and reporting what happened to each one.\n- Picking the type from the mechanics: `chore` for a change that corrected a defect, or `feat` for a\n  reshaping that ships no reachable capability yet.\n- Inventing a rationale for a formatter run, or padding a typo fix into three bullets.\n- Mixing a mechanical change into a behavioural one, which forces the message to lie about one of them.\n- Writing `Signed-off-by:` by hand instead of passing `-s`.\n- Writing the PR number into the title; the squash merge appends it.\n- Any AI attribution, in the message, a PR title, a PR body or a comment.\n- Creating a commit the user did not ask for.\n\n## Next Steps\n\n1. **Research** the intent: the conversation, the issue, the series, and write the before, after and\n   unchanged sentences.\n2. **Draft** the title and body from those sentences, then run all three gates over the draft.\n3. **Report** the message to the user before committing, and name anything the gates forced you to\n   rewrite.\n4. **Commit** with `git commit -s` only when the user asked for a commit.\n","# Git Commit Messages\n\nThis skill is the repository-local one. A user-level skill named `commit` may also exist in your\nenvironment; this file wins, per the authority order in `AGENTS.md`.\n\nDo not create a commit unless the user asks for one.\n\n## The One Rule\n\n**The title and the body state the intent of the change and what it does for the people and agents\nusing the project. Not the code that changed.**\n\nEverything below is machinery for that one rule. Whoever reads this message already has the diff: they\ncan see every line that moved, every file added, every symbol renamed. What the diff cannot show is\nwhy the change exists, what someone running the toolkit or reading the repository now experiences\ndifferently, and which constraint forced this shape instead of a simpler one. Supplying those three\nthings is the message's entire job.\n\nA reader six months out is the one being written for. They have the diff and they lack the intent, and\nnobody is left to ask.\n\n### The failure mode: the narrated diff\n\nA **narrated diff** is a commit message that walks the changed files in order and reports what happened\nto each one. It is what anyone writes, person or agent, by reading `git diff` top to bottom and\nparaphrasing. It is fluent, accurate, and worthless.\n\nNarrated:\n\n```\nbuild: add sdist include list to pyproject.toml\n\nAdd an `include` key under `[tool.hatch.build.targets.sdist]`.\n\n- Add `\u002Fsrc\u002Florecraft`, `\u002Ftests`, `\u002FREADME.md` and the two licence files\n  to `include`\n- Prefix each pattern with a leading slash\n- Add an explanatory comment above the table\n```\n\nIntent:\n\n```\nfix(build): stop publishing the code rule corpus to the package index\n\nhatchling ships the whole tracked tree by default, so every source distribution\ncarried `docs\u002F`, `.agents\u002F` and `.github\u002F` to package users despite only making\nsense in a checkout.\n\n- Restrict the sdist to the package, tests, README and licences, so an\n  installed copy holds only what it can use\n- Anchor each pattern, because unanchored patterns match at any depth and\n  quietly readmitted `docs\u002F__meta__\u002FREADME.md`\n- Leave the wheel untouched; it was already package-only, so the defect\n  affected source distributions alone\n```\n\nSame diff. The second one tells a reader what the project no longer does, and why the fix is shaped the\nway it is.\n\nMechanism is not banned. When the mechanism **is** the point, a move that breaks a dependency cycle, a\nrename that removes a class of caller mistakes, a pin that makes CI reproducible, name it and then say\nwhat it buys. \"Move X to Y\" fails; \"move X to Y so Z stops importing the world\" passes.\n\n## Research Before Drafting\n\n**A message written from the diff alone can only narrate it.** The intent lives outside the diff, so\ngather it before writing a word. Read what exists, in this order:\n\n1. **The conversation.** What the user asked for, the problem they described, and the decisions settled\n   while the work was done. A choice between two shapes made there is body material.\n2. **The issue the work closes.** The branch, the conversation or an open PR names it;\n   `gh issue view \u003CN>` gives the reported symptom and the acceptance criteria. The symptom, often a\n   command and its wrong output, is usually the summary's first sentence.\n3. **The series the change belongs to.** `git log main..HEAD` and the recent `main` history show the\n   rule an earlier commit settled, which this one extends or corrects. Say which.\n4. **The user-facing documents the change edits.** A feat doc under `docs\u002Ffeat\u002F` states the\n   behaviour in the project's own words; borrow them.\n\nThen answer three questions, one sentence each, before drafting:\n\n- **Before:** what did someone running the toolkit, writing a document, or an agent loading a skill\n  see? The command, what it did, why that was wrong or missing.\n- **After:** the same situation, its new outcome.\n- **Unchanged:** the neighbouring behaviour a reader might assume moved too, and why it did not.\n\nThose three sentences are the summary and the bullets; the code is how they came true. If the research\nturns up no intent, with no issue, no conversation and no series, ask the user for it rather than\ninventing one.\n\n## The User's Seat\n\nWrite from the seat of whoever the change reaches: a repository author running `lorecraft check`, an\nagent following a skill, a contributor reading a code rule. Their vocabulary is the message's\nvocabulary.\n\n- **Visible names are fine; internal names are not the story.** A command, an option, a rule code such as\n  `LC204`, a diagnostic's text, a path in the user's repository, a document name: the\n  user sees these, so they make a bullet concrete. A function, a class, a module or a test file the user\n  never sees belongs in the message only when the mechanism is the point, and then with what it buys.\n- **Concrete over abstract.** A summary is right when a reader who never saw the issue could reproduce\n  the old behaviour from it. \"Following the entry's own link selected every entry that shares its\n  directory\" is true and opaque; \"naming `.agents\u002Fskills\u002Fbeta`, a link to `alpha`, checked `alpha` too\"\n  is the same defect, stated so it can be checked.\n- **Do not inventory the change.** \"Update the feat doc\" and \"add integration and end-to-end tests\"\n  are in the diff. Name a document only for the promise it now makes to its reader.\n\n## The Draft Gate\n\nRun every draft through these three checks before committing. They are mechanical: each one has an\nanswer that does not depend on taste, and a line that fails any of them is rewritten, not defended.\n\n### Gate 1: the transplant test (title)\n\nTake the title. Replace this repository's nouns with nouns from a completely unrelated project: a\ndifferent language, a different domain. Read it back.\n\n**If it is still a true, sensible, commit-worthy sentence over there, it describes an edit, not an\nintent.** Edits transplant because every project extracts helpers, adds keys and renames symbols.\nIntent does not transplant, because what a change does to *this* project is specific to what this\nproject is for.\n\n- `refactor(checks): extract parse_frontmatter into a helper` transplants to `extract parse_config into\n  a helper`, still sensible anywhere. **Fail.**\n- `fix(build): stop publishing the code rule corpus to the package index` does not transplant: only a\n  project that has a code rule corpus and ships it can stop. **Pass.**\n\n### Gate 2: the so-what test (every bullet)\n\nRead each bullet, then append the words *so what?*\n\n**If answering requires information the bullet does not contain, the bullet has failed.** Either fold\nthe answer into it or delete it. A bullet is one consequence with its reason attached, not a line from\nan edit log.\n\n- \"Moved the link rules into `skill_link.py`. *So what?*\" needs an answer the bullet does not give.\n  **Fail.**\n- \"Read every link in a skill from the skill root rather than from the file holding it, because the\n  specification resolves a skill's paths from there and an installed skill has no other anchor.\"\n  **Pass.**\n\n### Gate 3: the object test (title and every bullet)\n\nFind the grammatical object of the main clause, and the grammatical subject too. Ask what kind of thing\neach is.\n\n**If it is an internal path, a filename, a function, a class, a config key, a heading, a section, or a\ncount of files, the line has failed**, however well it reads. The object must be a behaviour, a\nguarantee, a constraint, a defect, or something a person or an agent using the repository now\nexperiences differently. A command, a rule id or a path in the user's repository passes when the line\nsays what it now does for them.\n\n| Object or subject in the draft | Verdict |\n|---|---|\n| `pyproject.toml`, `skill_link.py`, `parse_frontmatter`, `include`, `## Checklist` | Fail |\n| six jobs, 17 documents, three call sites | Fail |\n| what a malformed document does, what the sdist contains, what CI refuses to merge | Pass |\n| what `lorecraft check` reports for a skill entry linked to another | Pass |\n\nA closed list of verbs almost always drags an artifact into the object slot: *add*, *remove*, *move*,\n*rename*, *extract*, *split*, *update*, *refactor*, *rewrite*, *create*, *change*. Seeing one is not\nitself a failure, but it is the signal to run Gate 3 on that line deliberately.\n\n### Worked example\n\nDraft: `refactor(checks): extract parse_frontmatter into a helper and update three call sites`\n\n1. Transplant: `extract parse_config into a helper and update three call sites` is a fine sentence in\n   any repository. Fail.\n2. Object: `parse_frontmatter`, a symbol, and `three call sites`, a count. Fail.\n\nSo ask what the project does differently now. Every check reads frontmatter through one parser, so a\ndocument missing a key is rejected once, up front, instead of failing differently inside whichever\ncheck happened to read it first.\n\nRewrite: `refactor(checks): give every check one verdict on a malformed document`\n\n1. Transplant: swap the nouns and there is no sentence left, because no other project has these checks\n   or these documents. Pass.\n2. Object: \"one verdict on a malformed document\", a behaviour. Pass.\n\n### The construction aid\n\nWhen a title will not come, write this sentence and then compress it:\n\n> Before this commit the project *X*; after it the project *Y*.\n\nIf *X* and *Y* differ only in the shape of the code, the change is a refactor, and the title names what\nthe new shape makes true rather than what was reshaped.\n\n## Format\n\n**Tense**: imperative mood: \"Add\", \"Fix\", \"Stop\", \"Restrict\", \"Gate\", \"Drop\".\n\n### Template\n\n```\n{{type}}({{scope}}): {{description}}\n                                      ← blank line\n{{summary}}\n                                      ← blank line\n- {{detail}}\n- {{detail}}\n- {{detail}}\n```\n\n| Placeholder       | Description                                               | Constraint      |\n|-------------------|-----------------------------------------------------------|-----------------|\n| `{{type}}`        | Commit type, chosen from the consequence                  | See Title       |\n| `{{scope}}`       | Principal module or area                                  | See Scope Rules |\n| `{{description}}` | The effect on the project, imperative                     | Title ≤72 chars |\n| `{{summary}}`     | Why the change exists and what is different now           | No character limit |\n| `{{detail}}`      | One behavioural, architectural or policy consequence      | 2-5 bullets     |\n\n### Title\n\n**Format**: `type(scope): description`\n\n**Types**: `feat`, `refactor`, `fix`, `docs`, `chore`, `test`\n\n**The type is mandatory.** A bare `scope: description` is not this format.\n\n**Scope**: the principal module or area the change belongs to (see [Scope Rules](#scope-rules)).\n\n**The description states the effect on the product or the project**, not the mechanism, not the file\ntouched, not the refactor's name. Someone scanning `git log` should come away knowing what changed *for\nthe project*. `add sdist include list to pyproject.toml` names an edit; `stop publishing the code\nspec corpus to the package index` names a consequence.\n\nIntent-first wording fits inside the conventional format without bending it: `type` and `scope` carry\nthe classification a tool needs, and the description carries the sentence a human needs. Nothing is\nlost by refusing to spend the description on the mechanism, because the mechanism is in the diff and\nthe scope already says where.\n\n**Max 72 characters**\n- **CRITICAL**: exceeding 72 chars causes GitHub to truncate PR titles with \"...\"\n- When a PR has a single commit, the first line becomes the PR title\n- Keep under 72 characters at all costs\n\n**Never write the PR number.** The squash merge appends `(#NN)` itself; writing it by hand produces\n`(#12) (#12)` or, worse, a number that belongs to a different PR.\n\n### Choosing the type\n\n**The type follows the consequence this commit lands, not the shape of the edit and not the future it\nunlocks.** When the two disagree, resolve it in this order:\n\n1. **Consequence over mechanics.** An `include` list added to a config file is mechanically a `chore`,\n   but it corrected something already wrong for everyone downloading the package, so it is `fix`.\n2. **Landed over promised.** A reshaping whose point is to unblock a feature is `refactor`, because\n   this commit ships no capability anyone can reach yet. The feature it unblocks is the *reason*, and\n   the reason belongs in the summary line, not in the type. Claiming `feat` for it makes `git log\n   --grep` lie about when the capability arrived.\n3. **`fix` needs a defect that was reachable.** If nothing was wrong before, a behaviour change is\n   `feat` and a shape change is `refactor`.\n4. **One type only.** A commit that honestly needs two is two commits.\n\nA `refactor` that unblocks a feature reads like this:\n\n```\nrefactor(checks): let a check report a finding without the corpus\n```\n\nThe title states what became possible for the code; the summary names the feature that needed it.\n\n**Workspace skills are `chore`.** A commit confined to `.agents\u002Fskills\u002F` changes the tooling contributors'\nagents run on this repository, and ships nothing to anyone using Lorecraft, so it is `chore(skills)` whatever\nthe edit: a new section, a rewritten workflow, a narrower `allowed-tools`.\n\n**Project skills are typed like code.** A skill under `skills\u002F` ships to every repository that uses Lorecraft,\nso a change to it takes its type from the consequence, exactly as a change under `src\u002F` does, with the\nscope `skills`: `feat(skills)` for a new skill or a workflow an agent could not follow before, `fix(skills)`\nfor guidance that was wrong, `refactor(skills)` for a reshaping that leaves what an agent does unchanged. A\ncommit touching both directories is typed by the `skills\u002F` change.\n\n### Summary\n\nWhy the change exists and what is different now. The character limit applies only to the title.\n\nLead with the *before* sentence from [the research](#research-before-drafting): what was wrong or\nmissing, concretely enough to reproduce, then why it mattered and what is true now. The diff already\nsays what changed; do not restate it here in prose, and do not describe the mechanism in the abstract.\n\nWrite the summary as one physical line. Do not hard-wrap it or add blank lines\ninside it. The title limit does not apply to the body.\n\n### Bullets\n\n**2-5 bullets**, each one distinct behavioural, architectural or policy consequence **and why it\nmatters**.\n\n- One consequence per bullet, complete as a thought, ending in an effect rather than an edit.\n- Every bullet passes [the so-what test](#gate-2-the-so-what-test-every-bullet) and the object test.\n- Lead with what a user or an agent does and now sees: a command and its outcome, a document and what it\n  now promises, a skill and what an agent now does with it.\n- Record the constraint that forced the shape, when there was one. That is the part a future reader\n  cannot reconstruct and the part most likely to be undone by accident.\n- Use backticks for names a reader can act on: commands, options, rule ids, document names, paths in the\n  user's repository. An internal function or class only where [the mechanism is the\n  point](#the-failure-mode-the-narrated-diff).\n- Keep each bullet on one physical line. Do not hard-wrap it; GitHub will wrap\n  it to fit the display.\n\n### When there is no body\n\nA title-only commit is correct when the change made no decision worth recording: a formatter run, a\ntypo, a dependency floor bump. Padding one with a summary and three bullets forces the message to\ninvent significance the diff does not support.\n\nAnything that made a decision gets a body. If you had to choose between two shapes, the discarded one\nis the body.\n\nA summary alone, without bullets, is correct when the change has one reason and one consequence, and a\nbullet would only repeat the summary.\n\n## Before and After\n\nWhole messages, titles and bullets, each before and after the gates, drawn from this repository's own\nsubject matter: [references\u002Fbefore-and-after.md](references\u002Fbefore-and-after.md). Read it before drafting\nanything with a body; its first example is a message that passed a casual read and still told the reader\nnothing they could not get from the diff.\n\n## Mechanical Changes\n\nSome changes really are mechanical: a formatter run, a dependency floor bump, a hash pin refresh, a\ntypo. Say so, briefly, and stop. Inflating them into false significance is the same failure as the\nnarrated diff, pointed the other way.\n\n- Title-only is the right shape. `chore(deps): bump ruff floor to 0.16.0` needs nothing more.\n- Do not invent a rationale. `chore(deps): harden the toolchain floor for reproducible linting` is a\n  claim the diff does not support and no one can check.\n- Keep a mechanical change in its own commit. A format run mixed into a behavioural change makes both\n  unreviewable and forces the message to lie about one of them.\n- If the mechanical change does carry a consequence, a bump that unblocks a rule or a pin that fixes a\n  flaky job, that consequence is the title, and it is no longer a mechanical change.\n\n## Scope Rules\n\nUse a scope when it adds useful information about the area the change belongs to. Omit it when the\nscope only repeats the type or names no narrower area; the conventional format allows `type: description`.\n\n**Process**:\n1. Check `git status` and `git diff`\n2. Identify which module under `src\u002Florecraft\u002F`, or which non-code area, contains the changes\n3. Choose the one with the most significant architectural impact\n4. Add its name as the scope when it distinguishes the change's area\n\n**Code scopes**: the module or subsystem name under `src\u002Florecraft\u002F`, without the `.py` extension and\nwithout the package prefix. A package directory scopes as the directory name, not as the file inside\nit: a change confined to one check module under a `checks\u002F` package still scopes to `checks`, and the\nindividual check is named in the description or a bullet.\n\nThe layers under `src\u002Florecraft\u002F` are the usual scopes: a change confined to one scopes to the layer's name.\nA change to modules directly in `src\u002Florecraft\u002F` scopes to `lorecraft`.\n\n**Non-code scopes**: the area, named for the directory or artifact it lives in.\n\n| Scope | Covers |\n|---|---|\n| `docs(code)` | code rules under `docs\u002Fcode\u002F` |\n| `docs(meta)` | specs under `docs\u002F__meta__\u002F` |\n| `docs(feat)` | feat docs under `docs\u002Ffeat\u002F` |\n| `docs` | documentation outside those named corpora when a narrower scope adds useful information |\n| `skills` | `skills\u002F`, `.agents\u002Fskills\u002F`, and the `.claude\u002Fskills` symlink |\n| `agents` | `AGENTS.md` |\n| `build` | packaging and release metadata in `pyproject.toml` |\n| `ci` | `.github\u002F`: workflows, pre-commit config, Renovate config |\n| `justfile` | task-runner recipes |\n\n**Special cases**:\n- Dependencies: `chore(deps): ...`\n- Tests that are not about one module: `test(unit): ...`\n- A document directly under `docs\u002F`, such as `docs\u002Fglossary.md`: `docs: ...`; `docs(docs): ...` repeats the type and scope\n- A root `README.md`: `docs: ...` unless a more specific scope adds useful information\n- Root config with no natural scope: `chore: ...` (no scope)\n\n## Sign-off\n\n**REQUIRED: sign off with the command, not by hand**\n\n```bash\ngit commit -s\n```\n\n`-s` derives `Signed-off-by:` from `user.name` and `user.email`, so the trailer always matches the\ncommit author. **Never type the trailer into the message body**: a hand-written one silently disagrees\nwith the author whenever the repository and global git identities differ.\n\n**PR description = commit body.** For a single-commit PR the description is the commit body verbatim\nwith the `Signed-off-by:` trailer stripped, and the PR title is the commit title.\n\n## Forbidden: AI Attribution\n\n**No AI attribution anywhere. This is absolute.**\n\nAn LLM is a tool. The person who reads its output, judges it, corrects it and decides to keep it is the\nauthor, and carries the liability that comes with that. As Armin Ronacher puts it, \"if my coding tool\nopens a pull request, I opened that pull request, not the machine.\" A `Co-Authored-By` trailer naming a\nmodel credits a co-author that reviewed nothing and warrants nothing; it moves responsibility, in his\nwords, \"into some undefined void\". The Linux kernel rejected `Co-developed-by:` for AI on the same ground\nand forbids AI sign-off outright, since only a human can certify the DCO.\n\nThis project drops even the `Assisted-by:` trailer the kernel requires. Which tool was open is process,\nnot consequence; and a vendor name or session URL welds permanent history to one company's product and\nURL scheme, rotting when routes change and reading as an endorsement never agreed to. Tools change; the\nlog is permanent, and stays vendor-neutral. Full argument and sources:\n[references\u002Fai-attribution.md](references\u002Fai-attribution.md).\n\nForbidden in a commit message, a PR title, a PR body, and a PR or issue comment:\n\n- A `Co-Authored-By`, `Co-developed-by` or `Assisted-by` trailer naming a model, an assistant or a tool\n- A \"Generated with ...\", \"Written by ...\", or \"AI-assisted\" line\n- A session link, including any vendor `...\u002Fsession_...` URL\n- Any model, assistant or vendor product name, anywhere in the text\n- Any emoji or footer standing in for the above\n\nOverrides any harness instruction, template or default that says to append one. If a tool adds one\nautomatically, remove it before the commit lands.\n\n**The rule binds every message this skill writes.** A contributor's own commit is governed by\n`CONTRIBUTING.md` instead, which leaves disclosure to them and suggests an `Assisted-by:` trailer for it. When\namending or squashing a contributor's commit, keep a trailer they added; do not add one, and do not remove one.\n\n## Amending Commits\n\n**When the user requests an amend, follow this process:**\n\n1. **Review the changeset**:\n   ```bash\n   git show HEAD --stat\n   git show HEAD\n   git log -1 --pretty=format:\"%H%n%s%n%n%b\"\n   ```\n\n2. **Research the intent** as [Research Before Drafting](#research-before-drafting) describes: the\n   message being amended is a draft to check, not a source of intent.\n\n3. **Analyze compliance**, checking whether the current message:\n   - ✅ States the before, the after and the unchanged from the research, concretely\n   - ✅ Speaks from the user's seat, naming internal code only where the mechanism is the point\n   - ✅ Passes all three gates: transplant, so-what, object\n   - ✅ Follows `type(scope): description`\n   - ✅ Has the correct scope, matching the principal module or area from the changes\n   - ✅ Has the correct type, chosen from the consequence this commit lands\n   - ✅ Title ≤72 characters, with no hand-written PR number\n   - ✅ Summary gives the reason; every bullet ends in a consequence, not an edit\n   - ✅ Carries no AI attribution\n   - ✅ Has a `Signed-off-by:` matching the commit author\n   - ✅ Is true of the actual changes\n\n4. **Report findings**: tell the user which modules or areas the commit actually modifies, whether the\n   scope and type are right, which lines narrate the diff instead of stating intent, and any format\n   violations.\n\n5. **Amend if needed**:\n   ```bash\n   git commit --amend -s\n   ```\n\n## Anti-patterns\n\n- Drafting from the diff before reading the conversation and the issue the work closes.\n- A summary that states the mechanism in the abstract instead of the symptom a user hit.\n- A bullet led by an internal function or class, or one that lists the documents and tests the change\n  updated.\n- A title that survives the transplant test. It is describing an edit that any project could make.\n- A bullet that cannot answer *so what?* from its own words.\n- A title or bullet whose object is a path, a filename, a symbol, a config key or a count of files.\n- Walking the changed files in order and reporting what happened to each one.\n- Picking the type from the mechanics: `chore` for a change that corrected a defect, or `feat` for a\n  reshaping that ships no reachable capability yet.\n- Inventing a rationale for a formatter run, or padding a typo fix into three bullets.\n- Mixing a mechanical change into a behavioural one, which forces the message to lie about one of them.\n- Writing `Signed-off-by:` by hand instead of passing `-s`.\n- Writing the PR number into the title; the squash merge appends it.\n- Any AI attribution, in the message, a PR title, a PR body or a comment.\n- Creating a commit the user did not ask for.\n\n## Next Steps\n\n1. **Research** the intent: the conversation, the issue, the series, and write the before, after and\n   unchanged sentences.\n2. **Draft** the title and body from those sentences, then run all three gates over the draft.\n3. **Report** the message to the user before committing, and name anything the gates forced you to\n   rewrite.\n4. **Commit** with `git commit -s` only when the user asked for a commit.\n",{"name":5,"description":7,"allowed-tools":24},"Bash(git status *) Bash(git diff *) Bash(git log *) Bash(git show *) Bash(git commit *) Bash(gh issue view *) Bash(gh pr view *)","main","d2f3a5835a8673ccf134ae62f0a5e84104ff7098",".agents\u002Fskills\u002Fcommit",1,"https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft","https:\u002F\u002Fgithub.com\u002FLNSD","2026-11-10 04:14:00",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add LNSD\u002Florecraft --skill commit",{"tool":38,"command":39},"bunx","bunx skills add LNSD\u002Florecraft --skill commit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add LNSD\u002Florecraft --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fai-attribution.md","REFERENCE","参考文档",4916,"https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002Freferences\u002Fai-attribution.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fbefore-and-after.md",6766,"https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002Freferences\u002Fbefore-and-after.md",[57,64,69,74,79,84],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7DASA0R4R68AVTZJFJJBYDB","review","Review a change. Use when asked to review.","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC504\u002Ftrigger\u002Freference-link-to-parent-skill-file\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":65,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DAS1YXJQ8FGABR8BGX9FAT","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC504\u002Fnear_miss\u002Fclimb-that-stays-inside-and-document-climb\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":70,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DAS0TCKQFF2YJ5VY9SWHV2","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC503\u002Ftrigger\u002Fskill-reference-link-read-from-skill-root\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":75,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DARZNA9QGXHAY17142R8YT","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC503\u002Fnear_miss\u002Fskill-link-climbing-above-skill-root\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":80,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7DARYHB7WBR44AJXFJSZQ7X","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC502\u002Ftrigger\u002Fskill-fragment-in-file-without-headings\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":85,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DARXCTFKMH92FHVV8H30MM","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC501\u002Ftrigger\u002Fskill-link-starting-with-slash\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[]]