You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2026. It is now read-only.
description: "Agent that reformats Markdown files using Semantic Line Breaks according to the full SemBr specification. The output must be raw Markdown with applied semantic line breaks. Do not parse or interpret the output."
4
+
---
5
+
6
+
# Task
7
+
8
+
Apply **Semantic Line Breaks (SemBr)** to all Markdown (`.md`)
9
+
documents in the current project.
10
+
11
+
The output must be **raw Markdown** text, rewritten according to the
12
+
specification below.
13
+
14
+
Do not include explanations, parsing, summaries, or comments — only
15
+
return the rewritten Markdown document(s).
16
+
17
+
## Specification
18
+
19
+
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
20
+
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this
21
+
document are to be interpreted as described in RFC 2119.
22
+
23
+
1. Text written as plain text or a compatible markup language MAY use
24
+
semantic line breaks.
25
+
2. A semantic line break MUST NOT alter the final rendered output of the
26
+
document.
27
+
3. A semantic line break SHOULD NOT alter the intended meaning of the text.
28
+
4. A semantic line break MUST occur after a sentence, as punctuated by a
29
+
period (.), exclamation mark (!), or question mark (?).
30
+
5. A semantic line break SHOULD occur after an independent clause as
31
+
punctuated by a comma (,), semicolon (;), colon (:), or em dash (—).
32
+
6. A semantic line break MAY occur after a dependent clause in order to
33
+
clarify grammatical structure or satisfy line length constraints.
34
+
7. A semantic line break is RECOMMENDED before an enumerated or itemized
35
+
list.
36
+
8. A semantic line break MAY be used after one or more items in a list in
37
+
order to logically group related items or satisfy line length
38
+
constraints.
39
+
9. A semantic line break MUST NOT occur within a hyphenated word.
40
+
10. A semantic line break MAY occur before and after a hyperlink.
41
+
11. A semantic line break MAY occur before inline markup.
42
+
12. A maximum line length of 80 characters is RECOMMENDED.
43
+
13. A line MAY exceed the maximum line length if necessary, such as to
44
+
accommodate hyperlinks, code elements, or other markup.
45
+
46
+
## Goals
47
+
48
+
1. For Writers:
49
+
The agent SHALL structure Markdown text so that the physical layout
50
+
of lines reflects the logical and semantic structure of the
51
+
author's thoughts.
52
+
2. For Editors:
53
+
The agent SHALL produce output that makes grammatical and
54
+
structural relationships easier to identify, supporting clear and
55
+
efficient editing without changing meaning.
56
+
3. For Readers:
57
+
The agent SHALL ensure that applied semantic line breaks do not
58
+
alter the rendered appearance or interpretation of the text in any
@@ -69,9 +82,18 @@ instruction allows its remote execution:
69
82
70
83
#### Notes on Environment Variables
71
84
72
-
-**OS_PROJECT_LIST**: Accepts project names from the [OpenStack Plugin Registry](https://docs.openstack.org/devstack/latest/plugin-registry.html). Multiple projects should be comma-separated (e.g., `OS_PROJECT_LIST=octavia,neutron,heat`)
73
-
-**Custom Configuration**: Any variable prefixed with `LINT_DEVSTACK_` will be automatically added to the Devstack local.conf file with the prefix removed (e.g., `LINT_DEVSTACK_OFFLINE=True` becomes `OFFLINE=True`)
74
-
-**Password Management**: Individual password variables override the generic `PASSWORD` variable for specific components
0 commit comments