DEV Community

Roberto Luna
Roberto Luna

Posted on

TL;DR

#playadev #buildinpublic #ai #productivity

TL;DR

I recently implemented a manual review requirement for automated content publishing to Dev.to and Bluesky using a safety feature. This change ensures that no LLM-generated content goes live without human review, addressing a critical issue in our content automation pipeline.

The Problem

The problem was that our automated content generation system was publishing content to Dev.to and Bluesky without proper review. This was due to a lack of safety checks in place, which could lead to incorrect or low-quality content being published. The error message we encountered was a 400 error when trying to move a document using the Craft API, indicating that the parentId field was ignored.

What I Tried First

Initially, I tried to fix the issue by updating the CLAUDE.md and CLAUDE_CODE_CONTEXT.md files to reflect changes in the Claude model. However, this approach did not address the root cause of the problem. I also attempted to create documents directly with a parentId using the Craft API, but this approach was unreliable due to post-create issues.

The Implementation

To solve the problem, I implemented a safety feature that requires manual review before publishing content to Dev.to and Bluesky. This was achieved by adding a new configuration option require_manual_review to the content-automation system.

// content-automation/metadata.json
{
  "require_manual_review": true,
  // ...
}
Enter fullscreen mode Exit fullscreen mode

I also updated the bluesky_en.json and bluesky_es.json files to include a new type field with value progress or avance, indicating the type of update.

// content-automation/bluesky_en.json
[
  {
    "type": "progress",
    "text": "Finally fixed the bug in .github/workflows/bluesky-daily.yml that was causing GitHub Actions to skip on saturdays"
  }
]
Enter fullscreen mode Exit fullscreen mode 
// content-automation/bluesky_es.json
[
  {
    "type": "avance",
    "text": "Finalmente resolví el bug en feed.controller.ts donde la suma de tiers no coincidía con el total de stats"
  }
]
Enter fullscreen mode Exit fullscreen mode

Key Takeaway

The key takeaway from this experience is the importance of implementing safety checks in automated content generation systems. By requiring manual review before publishing content, we can ensure that only high-quality content reaches our audience.

What's Next

In the future, I plan to investigate the issue with the Craft API's parentId field and explore alternative solutions for creating documents with a specific parent. Additionally, I will continue to monitor the performance of the content automation system and make adjustments as needed to ensure optimal results.

Tags

vibecoding #buildinpublic #contentautomation #safetyfeatures #devto #bluesky

Part of my Build in Public series — sharing the real process of building SaaS projects from Playa del Carmen, México.

Repo: zaerohell/content-automation · 2026-06-30

#playadev #buildinpublic

Top comments (0)