Skip to content

Revise SKILL.md for updated documentation process#1399

Open
justinegeffen wants to merge 2 commits intomasterfrom
justinegeffen-doc-skill-update
Open

Revise SKILL.md for updated documentation process#1399
justinegeffen wants to merge 2 commits intomasterfrom
justinegeffen-doc-skill-update

Conversation

@justinegeffen
Copy link
Copy Markdown
Contributor

Updated the skill documentation to reflect changes in input sources and workflow phases.

Updated the skill documentation to reflect changes in input sources and workflow phases.

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

netlify Bot commented May 7, 2026

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 76bb8be
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/69fcf23c81300a0008f95370
😎 Deploy Preview https://deploy-preview-1399--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.

@christopher-hakkaart
Copy link
Copy Markdown
Member

fix formatting

Copy link
Copy Markdown
Member

@christopher-hakkaart christopher-hakkaart left a comment

Choose a reason for hiding this comment

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

Looks good. I'd be tempted to make the scope narrower (specifically call out master branch and make it the docs repo unless otherwise specified. Just to keep things simple and clear, the more options, the more chance things could go wrong.


Also read `references/docusaurus-conventions.md` in this skill's directory for Seqera-specific formatting patterns (admonitions, link references, frontmatter, heading hierarchy).

**Confirm the PR target repo before doing anything else.** Ask the user which repo the eventual PR should target. Default to `seqeralabs/docs`, but offer alternatives like `seqeralabs/platform-enterprise_docs`, a fork, or a feature-specific repo. Hold onto the answer — you'll need it in Phase 6. Also confirm the base branch (default: `master` or `main`, whichever the repo uses).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should this just be seqeralabs/docs with the option of a manual input custom repo?

IMO, it seems like an unnecessary step to list other options when they will be low-usage.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do feel free to ignore, comment only

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