Skip to content

docs: Clean up editorial workflow documentation#1141

Closed
justinegeffen wants to merge 2 commits intomasterfrom
justine-editorialv3
Closed

docs: Clean up editorial workflow documentation#1141
justinegeffen wants to merge 2 commits intomasterfrom
justine-editorialv3

Conversation

@justinegeffen
Copy link
Contributor

Summary

Documentation cleanup to align with actual editorial workflow behavior and clarify skill deployment context.

Changes

1. Fixed trigger documentation (.claude/README.md)

Problem: Docs claimed workflow runs automatically on PR creation, but it's actually manual-only.

Changes:

  • ✅ Clarified workflow is triggered by /editorial-review command or manual dispatch
  • ✅ Updated "How it works" section to reflect actual behavior
  • ✅ Added clear warning: workflow does NOT run automatically
  • ✅ Reorganized trigger instructions for clarity

2. Added agent status table (.claude/README.md)

Problem: Unclear which agents are active vs disabled.

Changes:

  • ✅ Added table showing all agents with status indicators
  • ✅ Documented which agents are used in CI vs local-only
  • ✅ Added note about re-enabling clarity agent

3. Added deployment context to skills

Problem: Unclear which skills are used in CI/CD vs local-only.

Changes:

  • editorial-review: Documented CI/CD usage in docs-review.yml
  • openapi-overlay-generator: Documented CI/CD usage in generate-openapi-overlays.yml
  • platform-changelog-formatter: Clarified as local-only (not in CI/CD)

Motivation

As part of reviewing the editorial workflow evolution, found critical documentation bugs that could confuse contributors about when workflows trigger and which tools are automated.

Testing

  • Pre-commit hooks pass
  • No new files created (avoided unnecessary docs)
  • All changes in appropriate reference locations

Related

Part of editorial system cleanup and consolidation.

🤖 Generated with Claude Code

The docs-review.yml workflow is manual-only, triggered by /editorial-review
comment or workflow dispatch. Previous docs incorrectly stated it runs
automatically on PR creation.

Changes:
- Clarify workflow is entirely manual (no automatic triggers)
- Update trigger documentation with correct methods
- Reorganize "How it works" section for clarity
- Add clear warning about manual-only operation
- Add agent status table showing which agents are active/disabled

This aligns documentation with actual workflow behavior established
in justine-editorialv3 cleanup.
Add deployment sections to all three skills to clarify:
- Where each skill is used (local vs CI/CD)
- Which workflows invoke them
- How they're triggered
- Their specific purpose/scope

Skills updated:
- editorial-review: Used in docs-review.yml workflow
- openapi-overlay-generator: Used in generate-openapi-overlays.yml
- platform-changelog-formatter: Local-only, not in CI/CD

This helps developers understand which skills are automated vs manual-only.
@netlify
Copy link

netlify bot commented Feb 17, 2026

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit cf19d2e
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6994cecbc724340008010d0a
😎 Deploy Preview https://deploy-preview-1141--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@justinegeffen
Copy link
Contributor Author

Consolidated into #1140 (docs/clarify-on-demand-triggers) to avoid duplication.

@justinegeffen justinegeffen deleted the justine-editorialv3 branch February 17, 2026 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments