ci-hygiene

Detect and repair ESLint, secret-scanner, and TypeScript CI failures in GitHub Actions workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/H-Analytics --skill ci-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-hygiene
Source: https://github.com/Norfolk-Group/H-Analytics/tree/main/.agents/skills/ci-hygiene
Command: npx skills add https://github.com/Norfolk-Group/H-Analytics --skill ci-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents and repairs common continuous integration failures introduced by external code pushes or automated agents by removing unused imports/variables, surfacing TypeScript compilation errors, and reducing secret-scanner false positives so CI stays green and developer review is focused on meaningful changes.

Core Features & Use Cases

  • ESLint unused variables: Automatically removes unused imports, prefixes unused destructured bindings with an underscore, and prefixes unused const/let declarations to satisfy @typescript-eslint/no-unused-vars and keep warnings under CI thresholds.
  • Secret scanner false positives: Detects patterns in seed and module identifiers that trigger the repo's secret-scanner and documents or whitelists known false-positive patterns to avoid blocking CI.
  • TypeScript reporting: Runs tsc to capture compilation errors and produces clear reports for manual fixes when automated remediation is insufficient.
  • When to use: After git pulls/merges, when GitHub Actions fail, before pushing changes, or when collaborating with external agents that may introduce noisy changes.
  • Workflow integration: Supports a post-pull standard workflow that auto-fixes, stages changes for review, and documents CI-related adjustments for maintainers.

Quick Start

Run the repository CI hygiene script to auto-fix lint warnings, surface TypeScript errors, and flag secret-scanner false positives.

Frequently Asked Questions about ci-hygiene

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

FAQPage Schema
How do I automatically fix ESLint unused variables errors in GitHub Actions CI?

Automatically fix ESLint unused variables by removing unused imports, prefixing unused destructured bindings with an underscore, and prefixing unused const or let declarations to satisfy @typescript-eslint/no-unused-vars and keep CI warnings under threshold.

How do I resolve secret-scanner false positives blocking CI pipelines?

Resolve secret-scanner false positives by detecting patterns in seed and module identifiers that trigger the scanner, then documenting or whitelisting known false-positive patterns to prevent them from blocking CI pipelines.

Can I automatically repair TypeScript compilation errors before pushing code?

Automatically repair TypeScript compilation errors by running tsc to capture errors and producing clear reports for manual fixes when automated remediation is insufficient, ensuring typecheck issues are surfaced before pushing changes.

What's the best way to fix CI failures caused by external code pushes or automated agents?

Fix CI failures caused by external code pushes by running a post-pull standard workflow that auto-fixes lint warnings, surfaces TypeScript errors, flags secret-scanner false positives, and stages changes for developer review.

Does this CI auto-fix workflow preserve developer review of staged changes?

Yes, the CI auto-fix workflow preserves developer review by staging all automated adjustments and documenting CI-related changes for maintainers, ensuring developers review meaningful changes rather than noisy lint fixes.

When should I run CI hygiene auto-fixes for lint and typecheck issues?

Run CI hygiene auto-fixes after git pulls or merges, when GitHub Actions fail, before pushing changes, or when collaborating with external agents that may introduce noisy lint or typecheck modifications.