agent-ci

Runs GitHub Actions CI pipelines locally to validate code before pushing.

1|Updated Feb 19, 2025
One-click install
npx skills add https://github.com/trystan2k/favoritable-old --skill agent-ci-trystan2k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-ci
Source: https://github.com/trystan2k/favoritable-old/tree/main/.agents/skills/agent-ci
Command: npx skills add https://github.com/trystan2k/favoritable-old --skill agent-ci-trystan2k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the wasted time of pushing code changes only to discover GitHub Actions CI failures, letting you validate all required checks locally before sharing your work with your team.

Core Features & Use Cases

  • Local CI Parity: Runs the exact same GitHub Actions pipeline locally, ensuring your changes pass all linting, type checking, and test suites that remote CI will run.
  • Pause & Retry Workflow: Automatically pauses on step failure, letting you fix issues and retry only the failed step or resume from an earlier step without re-running the entire pipeline.
  • Use Case: When you've updated OAuth provider integration code in the API, use this Skill to run the full test, lint, and type check pipeline locally to catch errors early, avoiding failed remote CI runs and wasted review time.

Quick Start

Use the agent-ci skill to run the full GitHub Actions CI pipeline locally to validate your recent code changes before pushing to the remote repository.

Frequently Asked Questions about agent-ci

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

FAQPage Schema
How do I run GitHub Actions CI locally before pushing code?

You can run GitHub Actions CI locally to validate code changes before pushing by executing the exact remote pipeline on your machine, ensuring all linting, type checking, and test suites pass prior to submitting pull requests.

Can I pause and retry a failed GitHub Actions step during local testing?

Yes, local CI testing can automatically pause on step failure, allowing you to fix the issue and retry only the failed step or resume from an earlier step without re-running the entire GitHub Actions pipeline.

Do I need Docker and Node.js to run continuous integration pipelines locally?

Yes, you need Node.js 18+ and Docker installed to replicate the remote continuous integration environment and run the full GitHub Actions pipeline locally for accurate code validation.

What is the best way to validate code changes before submitting a pull request?

The best way to validate code changes before submitting a pull request is running the full GitHub Actions CI pipeline locally to catch linting, type checking, and test suite failures early, avoiding wasted remote CI run time.

Does local CI testing support machine-readable output for agent integration?

Yes, local GitHub Actions CI testing supports machine-readable JSON event output, enabling seamless integration with automated agent workflows and continuous integration pipelines for code validation.