seiton

Lint and auto-fix GitHub Actions workflow files and action metadata using the seiton CLI.

2|1|Updated May 11, 2019
One-click install
npx skills add https://github.com/guitarrapc/dotfiles-win --skill seiton-guitarrapc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seiton
Source: https://github.com/guitarrapc/dotfiles-win/tree/main/HOME/.agents/skills/seiton
Command: npx skills add https://github.com/guitarrapc/dotfiles-win --skill seiton-guitarrapc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? GitHub Actions workflows often contain security risks, unpinned actions, misconfigured permissions, and style inconsistencies that are hard to catch manually. This Skill lints and auto-fixes workflow files (.github/workflows/*.yml) and action metadata (action.yml) so repositories stay secure and consistent. ## Core Features & Use Cases - Linting with 60+ rules: Detect security issues (template injection, unpinned actions, credential leaks), correctness problems, and style violations across workflows and action metadata. - Auto-fix mode: Preview fixes with --fix --dry-run, then apply them with --fix, including SHA pinning of actions and digest pinning of container images. - Configurable policy: Tune rule severity, enable opt-in online audit rules, and scope exclusions per file or job via .github/seiton.yaml. - Use Case: When adopting seiton on a large repository for the first time, start with --min-severity error, preview fixes, tune the config, and iterate until only intended findings remain. ## Quick Start Use the seiton skill to lint the GitHub Actions workflows in this repository and apply safe auto-fixes.

Frequently Asked Questions about seiton

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint GitHub Actions workflow files with seiton?

Run seiton in the repository root to lint all files under .github/workflows and action.yml files. Use --min-severity error to focus on critical findings first, then run seiton --fix to apply automatic fixes.

How do I auto-fix GitHub Actions workflow issues?

Preview changes with seiton --fix --dry-run to see a unified diff, then apply them with seiton --fix. Rules like unpinned-uses, job-permissions-required, and template-injection support automatic remediation.

How do I pin GitHub Actions to commit SHAs?

Run seiton --fix --enable-pin-network to resolve action refs to commit SHAs via the GitHub API. This requires GITHUB_TOKEN or SEITON_GITHUB_TOKEN, and you can configure min-age-days and excluded branches in .github/seiton.yaml.

How do I suppress seiton warnings for specific files?

Add exclusions in .github/seiton.yaml with a file glob and optional rules list, for example excluding generated or legacy workflows. For one-off cases, use inline directives like '# seiton: disable-next-line <rule-id>'.

Why does seiton exit with code 1 even when only warnings are found?

Warnings-only runs exit 1 by default. Use --min-severity error in CI if warnings should not fail the job, or adjust rule severities in the config file.

Does seiton support online security audit rules?

Yes, rules like known-vulnerable-actions, impostor-commit, ref-confusion, and stale-action-refs are opt-in. Enable them in .github/seiton.yaml and provide GITHUB_TOKEN or SEITON_GITHUB_TOKEN for API access.