SkillAgentSearch skills...

ci

Run all CI checks locally, mirroring the GitHub Actions CI pipeline. This catches issues before creating a PR. Execute these steps in order, stopping on first failure. Report results as a summary table at the end. Run `npm run check` from the project root.

Install / Use

npx skills add antosubash/SimpleModule

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

61/100

Category

Automation

Supported Platforms

Claude Code

Our assessment of ci

ci scores 61/100 on our quality scale, 2731st of 2,877 Automation skills we index.

Its Claude Commands is 1.4 KB long, split into 6 sections and no code examples: moderately detailed.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
20/30
Structure
11/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 31 days ago, so ci is actively maintained.
  • Our last check on 2026-10-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ci compared with similar skills

All 4 of these similar skills score higher than ci; compare them before choosing.

SkillScoreStarsUpdatedFormat
ci (this skill)by antosubash61031d agoClaude Commands
claude-memby thedotmack100113.8ktodayCLAUDE.md
taste-skillby Leonxlnx100111.0k1d agoCLAUDE.md
Agent-Reachby Panniantong100109.5k1d agoCLAUDE.md
Understand-Anythingby Egonex-AI10091.0ktodayCLAUDE.md

Frequently asked questions

How do I install ci?
Run npx skills add antosubash/SimpleModule. The install tabs above show the steps for each supported agent.
Which AI agents does ci work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is ci safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ci still maintained?
The repository was last updated 31 days ago, so ci is actively maintained.

Run all CI checks locally, mirroring the GitHub Actions CI pipeline. This catches issues before creating a PR.

Execute these steps in order, stopping on first failure. Report results as a summary table at the end.

Step 1: Lint & Format Check

Run npm run check from the project root. This runs biome lint + format check, page validation (validate-pages), i18n validation (validate:i18n), framework-scope validation (validate:framework-scope), and TypeScript type checking (typecheck).

Step 2: Frontend Build

Run npm run build from the project root. This builds all module frontend assets via Vite in production mode.

Step 3: .NET Build

Run dotnet build from the project root. This compiles all .NET projects including source generators.

Step 4: .NET Tests

Run dotnet test --no-build from the project root. This runs all unit and integration tests (excluding load tests which are filtered out in CI).

Step 5: E2E Smoke Tests

Run npm run test:smoke -w tests/e2e to execute Playwright smoke tests. Playwright browsers are already installed.

Reporting

After all steps complete (or on first failure), print a summary table:

| Step | Status | |------|--------| | Lint & Format | pass/fail | | Frontend Build | pass/fail | | .NET Build | pass/fail | | .NET Tests | pass/fail | | E2E Smoke Tests | pass/fail |

If any step fails, show the relevant error output and suggest a fix.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
Updated1mo ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low
ci — Claude Commands: Install & Safety Check | SkillAgent