Full regression test of an existing article against the live portal. Use when articles may be stale and need end-to-end verification against the current portal UI before updating.
Add REST API coverage to an existing Customer Portal article with MethodSwitch and repository OpenAPI specs. Use when asked to add API coverage or create a REST API tab for a portal-only article.
Audit and update an existing documentation article by testing each step against the live Gcore portal. Use when asked to verify, audit, or fix an outdated article through portal testing.
Triage and work on a GitHub issue from G-Core/product-documentation one at a time. Use when the user asks to pick up an issue, work the issue queue, or gives an issue number or URL from https://github.com/G-Core/product-documentation/issues.
Write the opening paragraph(s) for a documentation tab or section. Use when adding or rewriting an intro for a MethodSection (Portal, REST API, Terraform, etc.) or any article section that needs a short lead-in.
Use this skill to triage and work on GitHub issues from G-Core/product-documentation one at a time. It fetches the issue via gh or GitHub API, checks whether the work is already on main, classifies the request, finds the affected MDX article, creates an issue/{number}-{slug} branch, routes to update-page, write-from-scratch, full-audit, or cookbook, and closes the loop with a PR that references Closes #N. Trigger when the user says "work on GitHub issues", "pick up issue #1845", "next issue from the queue", pastes a link to github.com/G-Core/product-documentation/issues/, or asks to start documentation work from the issue tracker. Use BEFORE loading other writing skills unless the user already completed triage. Do not use for Jira tickets (use jira-context instead).
Compile an end-to-end scenario guide that combines multiple Gcore products or sections into one article. Use when asked for a real-world guide spanning more than one product or section.
Draft documentation for new Gcore product features or product changes, research context, update or create the right article, and open a draft PR. Use when product teams provide feature context and want a documentation draft.