Skip to content

Conversation

@justinegeffen
Copy link
Contributor

@justinegeffen justinegeffen commented Dec 11, 2025

  • Added agents and a workflow to test how they work and scale
  • Based on publicly available documentation conventions.

Added Topic Structure Agent documentation for auditing compliance with CTRT framework.

Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Added voice-tone guidelines for documentation PRs, focusing on consistent voice, active tone, and present tense usage.

Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
@netlify
Copy link

netlify bot commented Dec 11, 2025

👷 Deploy Preview for seqera-docs processing.

Name Link
🔨 Latest commit 1b34840
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/697130969551430008e2d67d

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre-commit formatting suggestions

Pre-commit hooks found some formatting changes. You can apply each suggestion directly by clicking the "Commit suggestion" button, or run pre-commit locally and commit again.


1. Select **Launchpad** > **Add pipeline**.
2. Enter the repository URL.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

# Maximum files per review batch (prevents timeout on large PRs)
max_files_per_batch: 20

# Output format for PR comments
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Output format for PR comments

- major_change # Run when >50% of file changed

# File patterns (glob)
patterns:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
patterns:

Use the terminology agent to review these changed documentation files:
${{ needs.changes.outputs.docs_files }}
Check for:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Check for:

Use the clarity agent to review these changed documentation files:
${{ needs.changes.outputs.docs_files }}
Check for:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Check for:

Use the inclusive-language agent to review these changed documentation files:
${{ needs.changes.outputs.docs_files }}
Check for:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Check for:

const statusEmoji = {
'success': '✅',
'failure': '❌',
'skipped': '⏭️',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'skipped': '⏭️',

prompt: |
Use the docs-fix agent to apply fixes to all changed documentation files in this PR.
Apply fixes for:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Apply fixes for:

justinegeffen and others added 3 commits January 12, 2026 18:19
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre-commit formatting suggestions

Pre-commit hooks found some formatting changes. You can apply each suggestion directly by clicking the "Commit suggestion" button, or run pre-commit locally and commit again.

# Focus only on RNA-Seq issues
./lint --no-heading-case platform-enterprise_docs/

# Focus only on heading issues
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Focus only on heading issues
# Focus only on heading issues

- Reason: [Google style guide principle or grammar rule]

+ Line Y: [original text]
- Issue: [description of problem]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Issue: [description of problem]
- Issue: [description of problem]

- Specific line-by-line corrections
- Suggestions for improvement
- Explanations of Google style guide principles
- A revised version if requested
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- A revised version if requested
- A revised version if requested


# Documentation Linter Shortcut
# Usage: ./lint [options] [directories...]
#
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#
#

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre-commit formatting suggestions

Pre-commit hooks found some formatting changes. You can apply each suggestion directly by clicking the "Commit suggestion" button, or run pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Add changelog-formatter.skill.md to enable manual formatting and style
checking of Seqera changelogs (Platform, Wave, Nextflow, Fusion).

The skill applies universal style rules from the Seqera changelog style guide:
- Past tense, active voice, sentence case
- Product-specific requirements (attribution for Wave/Nextflow)
- Quality checks for consistency and formatting

Location: .claudeskills/ (standard location for Claude Code skills)
Add automated formatting and style enforcement for Platform Cloud and Enterprise changelogs.

Components added:
1. Manual skill (.claudeskills/platform-changelog-formatter.skill.md)
   - Format individual Platform changelogs on-demand
   - Applies component-based organization and universal style rules
   - Platform-only scope (Cloud and Enterprise)

2. Automated PR review agent (.github/.claude/agents/platform-changelog-style.md)
   - Automatically reviews Platform changelog changes in PRs
   - Enforces past tense, active voice, Studios capitalization
   - Requires component organization (Studios, Compute, Pipelines, etc.)
   - Fails PR if critical style violations found

3. Review configuration update (.github/.claude/agents/review-config.yaml)
   - Registered platform-changelog-style agent
   - Triggers on all Cloud/Enterprise changelog changes
   - Does NOT apply to Wave/Nextflow/Fusion changelogs

Scope: ONLY Seqera Platform Cloud and Enterprise changelogs
- changelog/seqera-cloud/*.md
- changelog/seqera-enterprise/*.md

Wave, Nextflow, and Fusion changelogs remain unchanged (keep attribution format).
Removed changelog-formatter.skill.md as it's redundant with the Platform-specific
formatter. We only need platform-changelog-formatter.skill.md which handles Cloud
and Enterprise changelogs.

Wave, Nextflow, and Fusion changelogs will remain in their current format
(with attribution) and don't need automated formatting.
…ASK]

Added explicit note in platform-changelog-formatter skill that component
headers MUST be level 3 headers (###), NOT bold (**Component**).

Updated in two places:
- Section 4 (component organization): Added CRITICAL note
- Section 7 (quality checks): Clarified the check

This ensures components are formatted as:
### Studios
NOT:
**Studios**
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

1 similar comment
@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪄 Pre-commit formatting suggestions

You can apply each suggestion via the GitHub UI, add a comment containing the keyword fix formatting or set up pre-commit locally and commit again.

else
# Pass all arguments through to the linter
node "$LINTER_PATH" "$@"
fi No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fi
fi

@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

1 similar comment
@github-actions
Copy link
Contributor

📝 Documentation Review Summary

Check Status
CTRT Topic Structure ❌ failure
Page Structure ❌ failure
Voice/Tone ❌ failure
Terminology ❌ failure
Clarity ❌ failure
Inclusive Language ❌ failure

Review powered by Claude Code SME agents

To apply fixes: Comment /fix-docs on this PR

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.

2 participants