running-in-ci_skill

Overview

This skill defines safe, repeatable rules for operating in GitHub Actions CI for the Worktrunk project. It focuses on protecting secrets, monitoring CI runs until green, and producing concise, well-structured PR comments. Use these rules whenever you push changes or review pull requests that trigger CI.

How this skill works

It enforces never exposing environment variables or credentials in outputs, comments, or logs. It guides operators to monitor CI runs with GitHub CLI commands, inspect failures, and iterate until all platform checks (Linux, Windows, macOS) succeed. It also prescribes a compact PR comment format with detailed findings placed inside collapsible sections.

When to use it

• After pushing a branch that triggers GitHub Actions for Worktrunk
• When monitoring CI status for pull requests across multiple OS runners
• Before posting any PR comment that might include sensitive information
• When diagnosing failing CI jobs and producing a public review summary

Best practices

• Never print or paste env variables, API keys, tokens, or file contents that contain credentials
• Use gh pr checks, gh run list --branch <branch>, and gh run watch to follow CI progress
• If a run fails, inspect with gh run view <run-id> --log-failed before commenting
• Keep the top-level PR comment a short overview and move file-level detail into <details> sections
• Do not add manual job or branch links in comments; automated tooling already inserts them
• Adopt a helpful, observational tone; avoid checklists and prescriptive task lists

Example use cases

• Push a fix for a failing Linux test, watch the run with gh run watch, and wait until all checks pass before completing the PR
• Review a contributor’s PR: give a brief summary and include a file-by-file breakdown inside <details> tags
• Diagnose a flaky Windows runner by using gh run view to capture failed logs and iterate locally before re-running CI
• Ensure no secret or environment output appears in your review comments or pasted logs