/**
 * Claude Code skill scanfixes for Factiii Pipeline plugin
 *
 * Installs the three "standard" Claude Code skills the team uses across every
 * factiii-pipeline repo, so any Claude Code session in any repo can rely on
 * the same `/commit`, `/push`, and `/prod-check` workflows being available
 * with the same gates.
 *
 *   ~/.claude/skills/commit/SKILL.md      — lint:fix + check-types gate, then commit
 *   ~/.claude/skills/push/SKILL.md        — scoped tests for changed code, then push
 *   ~/.claude/skills/prod-check/SKILL.md  — full pre-prod gate (lint/types/tests/build
 *                                            + branch diff vs production + secret scan
 *                                            + audit + auto-commit fixes)
 *
 * All three SKILL.md bodies are intentionally **generic across factiii-pipeline
 * repos**: they live once at ~/.claude/skills/ and are shared by every repo on
 * the machine, so they detect repo shape at runtime (apps/server, packages/*,
 * Prisma, etc.) rather than hardcoding paths from any one repo.
 *
 * Local-only (no SSH, no GITHUB_ACTIONS check). Stage: dev.
 * Severity: warning — missing skills don't break deploys, but having them
 * available is what enforces the gates the team relies on.
 *
 * OPT-IN: These are "host-machine fixes" — they write to ~/.claude/, which is
 * the developer's personal Claude Code config, not project state. Per
 * STANDARDS.md "Host-Machine Fixes", they are gated behind an explicit opt-in
 * in stack.local.yml (`claude_skills: true`). When the flag is unset or false,
 * scan returns "no issue" and fix is a no-op. This keeps devs who don't use
 * Claude Code (or who curate their own skills) from being surprised by files
 * appearing in their home directory.
 *
 * REFRESH BEHAVIOR: Unlike the previous scanfix (which only wrote when the
 * file was missing), this one **overwrites when the on-disk content drifts
 * from the canonical content baked into stack**. That way `npx stack fix --dev`
 * propagates skill updates to every dev who has opted in. If a dev wants to
 * customize their local copy and not have stack stomp it, they can add the
 * line `<!-- user-managed -->` anywhere in the file — the scanfix will detect
 * the marker and skip that file.
 *
 * Split of concerns:
 *   - This scanfix owns the skill *workflows* (SKILL.md content). Process
 *     lives here so it ships with stack and is identical on every dev machine
 *     that opts in.
 *   - The audit *override reference table* (which packages, why) is optional
 *     per-repo at .specs/audit.md so PR reviewers can see it; the prod-check
 *     skill uses it if present and skips it if not.
 *   - Phase 4 of the prod-check SKILL.md auto-commits the deterministic fixes
 *     the gate produced. This is a sanctioned exception to factiii-stack's
 *     "never commit without approval" rule because prod-check is itself an
 *     explicit user-invoked gate; the skill always reports the resulting
 *     commit SHA back to the user.
 */
import type { Fix } from '../../../../types/index.js';
export declare const claudeSkillFixes: Fix[];
//# sourceMappingURL=claude-skills.d.ts.map