Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

gfm

Estrellas8

Forks0

Actualizado31 de enero de 2026 a las 05:34

Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

ivy

ivy/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Redactores técnicosArtes, diseño, entretenimiento, deportes y medios·SOC 27-3042

SKILL.md

readonly

name	gfm
description	Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)
argument-hint	[file \| topic \| review]

GitHub-Flavored Markdown

Arguments

$ARGUMENTS

Instructions

Parse arguments to determine task:

File path → Write/edit markdown file
"review" → Audit existing markdown for GFM best practices
Topic/description → Draft markdown content

Writing Guidelines

Structure:

Use heading hierarchy (# through ######)—GitHub auto-generates TOC for 2+ headings
Prefer ATX headings (#) over Setext (===)
One blank line before headings

Text styling:

Style	Syntax
Bold	`text`
Italic	`_text_`
Bold+italic	`*text*`
Strikethrough	`~~text~~`
Code	`code`
Subscript	`<sub>x</sub>`
Superscript	`<sup>2</sup>`

Code blocks:

```language
code here
```

Lists:

Unordered: use - consistently
Ordered: 1., 2., etc.
Task lists: - [ ] incomplete, - [x] complete
Nest by aligning under parent text

Links:

Inline: [text](url)
Section anchors: [text](#heading-name) (lowercase, hyphens, no punctuation)
Relative paths for repo files: docs/CONTRIBUTING.md

Images: ![alt text](url) — always include alt text

Alerts (callouts):

> [!NOTE]
> Useful information

> [!TIP]
> Helpful advice

> [!IMPORTANT]
> Essential info

> [!WARNING]
> Urgent attention

> [!CAUTION]
> Risk warning

Footnotes:

Text with footnote[^1].

[^1]: Footnote content.

Color swatches: `#FF5733`, `rgb(255,87,51)`, `hsl(11,100%,60%)`

Review Checklist

When reviewing markdown:

Heading hierarchy is logical (no skipped levels)
Code blocks specify language for syntax highlighting
Links use relative paths for repo files
Images have meaningful alt text
Task lists use proper syntax
Alerts use correct > [!TYPE] format
No trailing whitespace except intentional line breaks
Tables are properly aligned

Examples

/gfm README.md                → Edit/create README
/gfm review docs/             → Audit markdown files in docs/
/gfm API documentation        → Draft API docs content
/gfm changelog entry          → Write changelog in GFM style

Más de este repositorio

mismo repositorio

ivy/dotfiles

Use when checking Buildkite CI/CD builds, investigating failures, viewing job logs, or answering questions about pipeline status.

2026-06-048

handoff

ivy/dotfiles

Write a handoff brief summarizing the current conversation so a fresh agent can pick up the work. Writes to a file if given, otherwise copies to the clipboard.

2026-05-298

ivy/dotfiles

Use when bootstrapping hk pre-commit hooks for a project.

2026-05-298

mise

ivy/dotfiles

Use when adding, updating, troubleshooting, or managing mise tool dependencies. Supplements /install with mise-specific context about backends, lockfiles, and the github-first policy.

2026-04-058

allow

ivy/dotfiles

Add a tool pattern to the global Claude Code permissions allow list in bin/sync-claude-settings

2026-04-048

label-issue

ivy/dotfiles

Use when labeling GitHub issues or triaging the backlog. Applies the project's label taxonomy from docs/labels.md.

2026-03-028

name	gfm
description	Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)
argument-hint	[file \| topic \| review]

GitHub-Flavored Markdown

Arguments

$ARGUMENTS

Instructions

Parse arguments to determine task:

File path → Write/edit markdown file
"review" → Audit existing markdown for GFM best practices
Topic/description → Draft markdown content

Writing Guidelines

Structure:

Use heading hierarchy (# through ######)—GitHub auto-generates TOC for 2+ headings
Prefer ATX headings (#) over Setext (===)
One blank line before headings

Text styling:

Style	Syntax
Bold	`text`
Italic	`_text_`
Bold+italic	`*text*`
Strikethrough	`~~text~~`
Code	`code`
Subscript	`<sub>x</sub>`
Superscript	`<sup>2</sup>`

Code blocks:

```language
code here
```

Lists:

Unordered: use - consistently
Ordered: 1., 2., etc.
Task lists: - [ ] incomplete, - [x] complete
Nest by aligning under parent text

Links:

Inline: [text](url)
Section anchors: [text](#heading-name) (lowercase, hyphens, no punctuation)
Relative paths for repo files: docs/CONTRIBUTING.md

Images: ![alt text](url) — always include alt text

Alerts (callouts):

> [!NOTE]
> Useful information

> [!TIP]
> Helpful advice

> [!IMPORTANT]
> Essential info

> [!WARNING]
> Urgent attention

> [!CAUTION]
> Risk warning

Footnotes:

Text with footnote[^1].

[^1]: Footnote content.

Color swatches: `#FF5733`, `rgb(255,87,51)`, `hsl(11,100%,60%)`

Review Checklist

When reviewing markdown:

Heading hierarchy is logical (no skipped levels)
Code blocks specify language for syntax highlighting
Links use relative paths for repo files
Images have meaningful alt text
Task lists use proper syntax
Alerts use correct > [!TYPE] format
No trailing whitespace except intentional line breaks
Tables are properly aligned

Examples

/gfm README.md                → Edit/create README
/gfm review docs/             → Audit markdown files in docs/
/gfm API documentation        → Draft API docs content
/gfm changelog entry          → Write changelog in GFM style