From a80d8e003f663f39981f47a2311e5fcd3f55f0e0 Mon Sep 17 00:00:00 2001 From: Cam Date: Fri, 21 Nov 2025 22:23:29 +0000 Subject: [PATCH 1/3] Add additional instructions for reviewing blog posts related to new Pulumi features --- .claude/commands/docs-review.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.claude/commands/docs-review.md b/.claude/commands/docs-review.md index 1a285c0a5b9f..24c9410ab927 100644 --- a/.claude/commands/docs-review.md +++ b/.claude/commands/docs-review.md @@ -181,3 +181,14 @@ When reviewing **Blog posts or marketing materials**, serve the role of a profes - Reject filler, vague generalities, or AI-generated slop. - Avoid clickbait phrasing. - Clear call-to-action at the end. + +### Additional Instructions + +When blog posts introduce or announce new Pulumi features, providers, or significant functionality changes: + +1. Check if corresponding documentation exists in `content/docs/` for the feature being announced +2. Verify that API documentation, tutorials, or guides adequately cover the new functionality +3. If documentation is missing or incomplete, note this in your review with: + - Specific gaps identified (e.g., "No ESC integration guide found") + - Suggested documentation locations (e.g., "Should add to `content/docs/esc/guides/`") + - Recommended documentation type (tutorial, concept guide, API reference, etc.) From 52169fe41b0dec491db97dc552979a69c4c20305 Mon Sep 17 00:00:00 2001 From: Cam Date: Fri, 21 Nov 2025 22:30:26 +0000 Subject: [PATCH 2/3] Fix formatting in documentation review instructions for clarity --- .claude/commands/docs-review.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.claude/commands/docs-review.md b/.claude/commands/docs-review.md index 24c9410ab927..627b89f10fa9 100644 --- a/.claude/commands/docs-review.md +++ b/.claude/commands/docs-review.md @@ -189,6 +189,6 @@ When blog posts introduce or announce new Pulumi features, providers, or signifi 1. Check if corresponding documentation exists in `content/docs/` for the feature being announced 2. Verify that API documentation, tutorials, or guides adequately cover the new functionality 3. If documentation is missing or incomplete, note this in your review with: - - Specific gaps identified (e.g., "No ESC integration guide found") - - Suggested documentation locations (e.g., "Should add to `content/docs/esc/guides/`") - - Recommended documentation type (tutorial, concept guide, API reference, etc.) + - Specific gaps identified (e.g., "No ESC integration guide found") + - Suggested documentation locations (e.g., "Should add to `content/docs/esc/guides/`") + - Recommended documentation type (tutorial, concept guide, API reference, etc.) From 4cdbc97f33406c0627ed0a7b75ccdf9fa6ac46a3 Mon Sep 17 00:00:00 2001 From: Cam Date: Fri, 21 Nov 2025 23:34:48 +0000 Subject: [PATCH 3/3] Refine instructions for reviewing blog posts to enhance clarity and consistency --- .claude/commands/docs-review.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.claude/commands/docs-review.md b/.claude/commands/docs-review.md index 627b89f10fa9..a942e78ad9c9 100644 --- a/.claude/commands/docs-review.md +++ b/.claude/commands/docs-review.md @@ -187,8 +187,8 @@ When reviewing **Blog posts or marketing materials**, serve the role of a profes When blog posts introduce or announce new Pulumi features, providers, or significant functionality changes: 1. Check if corresponding documentation exists in `content/docs/` for the feature being announced -2. Verify that API documentation, tutorials, or guides adequately cover the new functionality +2. Verify that documentation, tutorials, or guides adequately cover the new functionality 3. If documentation is missing or incomplete, note this in your review with: - Specific gaps identified (e.g., "No ESC integration guide found") - Suggested documentation locations (e.g., "Should add to `content/docs/esc/guides/`") - - Recommended documentation type (tutorial, concept guide, API reference, etc.) + - Recommended documentation type (tutorial, concept guide, reference, etc.)