simplify-and-harden-ci

Run a CI-only variant of Simplify & Harden in pull requests:

pskoett/pskoett-ai-skills|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use simplify-and-harden-ci on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add simplify-and-harden-ci

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/pskoett/pskoett-ai-skills --skill simplify-and-harden-ci

Fetches simplify-and-harden-ci from pskoett/pskoett-ai-skills and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/simplify-and-harden-ci

Restart Cursor to activate simplify-and-harden-ci. Access via /simplify-and-harden-ci in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Context Limitation (Important)

CI agents do not have the same peak implementation context as the coding agent that wrote the change. Treat CI findings as structured review signals, not as full intent-aware rewrites.

Implications:

Prefer scan/report and merge gating

Do not auto-apply code changes in CI

Escalate ambiguous findings to interactive review

CI Contract

The CI skill must enforce:

Scope lock: review only files changed in the PR

Headless execution: report findings, do not apply patches/refactors

Structured output: emit simplify_and_harden summary payload

Gate policy:

critical: fail check when critical harden findings exist
advisory (optional): fail check when advisory findings are configured to block

Authoring Workflow (gh-aw)

Example-only template lives in references/workflow-example.md. Keep it outside .github/workflows until you explicitly want automation enabled.

When ready to enable:

Copy references/workflow-example.md template block into .github/workflows/simplify-and-harden-ci.md.

Compile and validate workflow:

gh aw compile --validate --strict

Trigger and push workflow changes:

gh aw run simplify-and-harden-ci --push

Check status/logs in GitHub Actions and ensure PR feedback is posted.

Prompt Template (CI)

Use this prompt body in your gh-aw workflow:

Run Simplify & Harden in CI (headless mode) for this pull request. Rules: 1) Review only files changed in this PR. 2) Do not modify repository files. 3) Before reporting findings, re-read all changed code with "fresh eyes" and actively look for obvious bugs, errors, confusing logic, brittle assumptions, naming issues, and missed hardening opportunities. 4) Simplify pass: detect dead code, naming clarity issues, control-flow complexity, unnecessary API surface, and over-abstraction. 5) Harden pass: detect input-validation gaps, injection vectors, auth/authz issues, secret exposure, data leaks, and concurrency risks. 6) Document pass: suggest non-obvious rationale comments as findings (do not edit files). 7) Emit structured YAML under key `simplify_and_harden`, including: - simplify findings - harden findings (critical/advisory split) - summary counts - `review_followup_required` - learning loop candidates for self-improvement ingestion 8) If blocking policy is enabled and matching findings exist, mark the run as failed.

simplify-and-harden-ci

Installation Guide

How to use simplify-and-harden-ci on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Simplify & Harden CI

Install

Purpose

Context Limitation (Important)

Prerequisites

CI Contract

Authoring Workflow (gh-aw)

Prompt Template (CI)

Recommended Outputs

Integration with Self-Improvement

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

grill-me

premortem

deslop

framer-motion

write-a-prd

travel-planner

Reviews

Discussion