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
Copy file name to clipboardExpand all lines: .github/skills/seo-geo-aeo-review/SKILL.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,11 @@ For focused front matter `description` edits only, use `.github/skills/metadata-
23
23
24
24
## Workflow
25
25
26
+
On any given page:
27
+
26
28
1. Identify the target content type and target developer intent.
27
-
2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading. If you've previously read a page, use context and don't re-read it unless there's a change since the last read.
28
-
3.State the page's owned task in one sentence. If the task is unclear or too broad, flag it.
29
+
2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading. If you've previously read the page, use context and don't re-read it unless asked to.
30
+
3.Summarize the page's owned task in one sentence. If the task is unclear or too broad, flag it.
29
31
4. Review SEO signals:
30
32
- The title is task-led and includes the main technology, platform, or tool.
31
33
- The `description` is one concise sentence that states the task, context, and outcome.
Copy file name to clipboardExpand all lines: .github/skills/writing-style-review/SKILL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,10 @@ Use this skill for granular prose, voice, readability, terminology, and style re
10
10
## Workflow
11
11
12
12
1. Identify the target file, section, or selected text.
13
-
2. Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use context and don't re-read it unless there's a change since the last read.
13
+
2. Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use context and don't re-read it unless asked to.
14
14
3. Review the target against the guidelines defined in this skill.
15
15
4. Depending on request type, do the following:
16
-
- For review requests, report high-impact style issues by file and line when possible.
16
+
- For review requests, report style issues by file and line when possible, ordered by severity.
17
17
- For edit requests, make focused rewrites, then re-open changed sections to check Markdown, shortcodes, links, and code fences.
0 commit comments