Skip to content
Skills Library
Programming · Review & audit

org-inline-code-spacing

/org-inline-code-spacing

生成或修改任何 Emacs org-mode 文本(.org 文件、聊天里的 org 片段、commit message 里的 org 语法)时使用:行内标记 =text= 与 *bold*、/italic/ 等强调标记必须与中文和标点保持半角空格边界;禁止用 **bold** 伪装标题,禁止用 Markdown backtick 当代码标记。Use when writing or editing Emacs org-mode text.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

生成或修改任何 Emacs org-mode 文本(.org 文件、聊天里的 org 片段、commit message 里的 org 语法)时使用:行内标记 =text= 与 *bold*、/italic/ 等强调标记必须与中文和标点保持半角空格边界;禁止用 **bold** 伪装标题,禁止用 Markdown backtick 当代码标记。Use when writing or editing Emacs org-mode text.

Original author description

生成或修改任何 Emacs org-mode 文本(.org 文件、聊天里的 org 片段、commit message 里的 org 语法)时使用:行内标记 =text= 与 *bold*、/italic/ 等强调标记必须与中文和标点保持半角空格边界;禁止用 **bold** 伪装标题,禁止用 Markdown backtick 当代码标记。Use when writing or editing Emacs org-mode text.

How it works

  1. 通用原则
  2. =code= 标记
  3. 强调标记(bold 等)同款边界约束
  4. 本次教训总结(2026-08-20 新增,三类高频违规)
  5. 禁止事项
  6. 验收步骤
Original SKILL.md headings · 57 lines, 185 words
SKILL.md preview
---
name: org-inline-code-spacing
description: 生成或修改任何 Emacs org-mode 文本(.org 文件、聊天里的 org 片段、commit message 里的 org 语法)时使用:行内标记 =text= 与 *bold*、/italic/ 等强调标记必须与中文和标点保持半角空格边界;禁止用 **bold** 伪装标题,禁止用 Markdown backtick 当代码标记。Use when writing or editing Emacs org-mode text.
---

# Org-mode 行内标记空格约束

生成 Emacs org-mode 文档(`.org` 文件或任何 org 语法文本)时,行内标记必须遵守边界空格约束。本规范覆盖两类标记:原文/代码标记 `=text=` 与强调标记(`*bold*`、`/italic/`、`_underline_`、`+strike+`、`~code~`)。

## 通用原则

- 标记**内侧**紧贴内容(`=text=`,不是 `= text =`)。
- 标记**外侧**必须各紧邻一个半角空格(U+0020,不是全角空格 ` `,也不是不换行空格);或位于行首/行尾。
- 无论旁边是中文、半角标点(`,.`)还是全角标点(`,。、`),外侧空格都不能省略。
- 原因:org-mode 只允许标记边界是空白或极少数允许字符;中文与标点不在允许集合内,任何一侧紧贴都会导致标记被当作普通文本。

## `=code=` 标记

唯一正确写法:

`今天是 =一个= 晴天`

以下写法一律禁止(两侧只要有一侧紧贴,渲染就不符合预期):

- `今天是=一个=晴天`
- `今天是=一个= 晴天`
- `今天是 =一个=晴天`
- `今天是=一个=,晴天`
- `今天是,=一个=晴天`
- `今天是,=一个=。晴天`
- `今天是一个=晴天=。`

## 强调标记(`*bold*` 等)同款边界约束

强调标记与 `=code=` 遵守完全相同的边界规则:内侧紧贴、外侧空白。与中文或标点紧贴即失效:

- 错误:`是**只读**的`、`(**已处理**)`、`**空(默认)**:`
- 正确:`是 **只读** 的`、`( **已处理** )`

## 本次教训总结(2026-08-20 新增,三类高频违规)

1. **开标记左侧紧贴标点**:`:=X=`、`,=X=`、`(=X=`、`;=X=`、`、=X=` 都是错的 → 必须 `: =X=`、`, =X=`、`( =X=`。
2. **标记内容与 `=` 之间误留空格**:`= X =`、`=X =` 都是错的 → 必须 `=X=`。
3. **闭标记右侧紧贴标点**:`=X=` 直接跟 `,`/`。`/`、`/`)`/`(`/`;`/`:` 都是错的 → 必须 `=X= ,`、`=X= )` 等。

## 禁止事项

- 禁止用 `**bold**` 伪装标题(如 `**.git 例外**`)→ 用真正的标题行 `* 标题`、`** 标题`、`*** 标题`。
- 禁止在 org 文档中混用 Markdown backtick 当代码标记 → org 的代码标记是 `=code=`。
- 不确定强调边界是否正确时,宁可不用强调,改用 `=code=` 标记或纯文本。

## 验收步骤

生成或修改任何 org 文本(`.org` 文件、聊天里的 org 片段、commit message 里的 org 语法)后,发送或提交前按顺序执行:

1. **配对扫描。** 逐行从行首向右配对标记(跳过 `#+BEGIN_SRC`/`#+BEGIN_EXAMPLE` 块与 `#+` 行):开标记左侧必须是行首或一个半角空格,闭标记右侧必须是行尾或一个半角空格。`=a= =b=` 合法;`甲=a= 乙`、`=a=乙` 不合法。
2. **内侧扫描。** 每对标记之间不得出现首尾空格:`= a=`、`=a =`、`= a =` 都判失败。
3. **强调同规。** 对 `*bold*`、`/italic/`、`_underline_`、`+strike+`、`~code~` 重复第 1–2 条,判定标准与 `=code=` 相同。
4. **渲染确认。** 有 Emacs 时用 `emacs file.org` 打开:标记应按 org 语法着色,而不是被当作普通字符。纯聊天输出无法渲染时,以第 1–3 条为通过标准。
5. **零例外交付。** 任一失败改到通过再交付;不确定时按「禁止事项」最后一条降级为 `=code=` 或纯文本。
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named org-inline-code-spacing.

Database snapshot: 13.11.2026 · package version e6a1bd8992f8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100emacs
    Expert GNU Emacs assistance covering init.el, Elisp, Org-mode, Magit, LSP Mode, and packages. Use when customizing Emacs, writing Elisp, and operating extensible keyboard-centric developer environments.
  • 86emacs-academic-writing
    Use Emacs for academic writing, research, and publication preparation with Org-mode and LaTeX. Trigger on phrases like "academic writing in emacs", "emacs academic workflow", "research in emacs", "org-mode thesis", "emacs latex writing".
  • 86major-mode-developer
    Develop Emacs major modes for language support and specialized editing. Trigger on phrases like "major mode development", "create a major mode", "emacs mode developer", "syntax highlighting emacs", "new emacs major mode".
  • 95emacs-lisp
    Expert guidance for writing professional Emacs Lisp code following the community-driven Emacs Lisp Style Guide by Bozhidar Batsov. Covers layout, naming conventions, syntax preferences, macros, documentation, and best practices. Use this skill when writing Emacs configuration,…
  • 100code-commit
    Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.
  • 90org-search
    Search and browse org-mode documents via the org MCP server. Use when the user wants to find content across org files, list their org documents, read file contents, or navigate headings and outlines. Triggers: "search my notes for...", "find org pages about...", "list my org…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.