stand-ci

Define CI/CD pipeline and GitHub Actions security best practices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lgtm-hq/claude-skills --skill stand-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stand-ci
Source: https://github.com/lgtm-hq/claude-skills/tree/main/skills/stand-ci
Command: npx skills add https://github.com/lgtm-hq/claude-skills --skill stand-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining secure and reliable CI/CD pipelines and GitHub Actions by providing clear guidelines and best practices.

Core Features & Use Cases

  • Workflow Security: Enforces pinning actions to commit SHAs to prevent supply chain attacks.
  • Best Practice Guidance: Offers standardized standards for scripting, action referencing, and version control.
  • Use Case: Developers can structure their CI/CD workflows to enhance security, repeatability, and maintainability following these standards.

Quick Start

Follow the provided guidelines to pin all actions in your workflow to specific commit SHAs to improve security.

Frequently Asked Questions about stand-ci

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

FAQPage Schema
How do I secure GitHub Actions workflows against supply chain attacks?

To secure GitHub Actions workflows against supply chain attacks, you should pin all referenced actions to specific commit SHAs. This ensures reproducibility and prevents unauthorized modifications from tag reassignments.

What are the best practices for organizing scripts in a CI/CD pipeline?

Best practices for organizing scripts in a CI/CD pipeline involve standardizing scripting conventions and following specific organization rules. This approach enhances workflow maintainability and consistency across DevOps automation processes.

Why should I pin GitHub Actions to commit SHAs instead of version tags?

Pinning GitHub Actions to commit SHAs instead of version tags guarantees workflow immutability and security. Tag reassignments can introduce malicious code, whereas commit SHAs provide a fixed, verifiable reference for your CI/CD pipeline.

Can I use these CI/CD standards to standardize automation processes across multiple DevOps teams?

Yes, you can use these CI/CD standards to standardize automation processes across multiple DevOps teams. The guidelines provide detailed conventions for workflow consistency, scripting, and action referencing suitable for software engineers.

What is the best way to ensure reproducibility in CI/CD pipeline development?

The best way to ensure reproducibility in CI/CD pipeline development is by enforcing action pinning and adhering to standardized version control conventions. These practices secure workflows and maintain consistent automation execution.