Results for “pre-commit-hook”

Runs before every git commit on heleni-memory. Checks: no credentials in tracked files, no oversized files, valid SKILL.md frontmatter for any new/modified skill. Triggers: "commit", "before push", "validate repo", or auto-runs as a git pre-commit hook.

Runs a two-wave validation pipeline (deterministic checks then rule-based checks) before every git commit, writing a sentinel file that a pre-commit hook enforces. Includes optional quick mode (first wave only) and a fix loop with up to three iterations.

Use when a commit's changes are finished and about to be presented for review. Runs the checks that catch the objections the user would otherwise raise, before they spend time reviewing.

Speckit Implement

Generates ultra-compressed commit messages in Conventional Commits format with a subject line ≤50 characters and a body only when the 'why' isn't obvious.

Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.

在启动高风险项目或重要决策前，需要预先识别潜在失败点以增强心理韧性和方案鲁棒性时

Before any cold touch on a target account, find and rank every warm way in. Inventories your team's collective network, customers, past colleagues, investors, and community overlap, scores each path, picks one connector, and writes the forwardable intro request. Built for B2B sellers, customizable to your network sources and CRM. Trigger on "warm intro path", "who can intro me", "bridge before cold", "warm path into this account", "find a referral path".

The pre-share gate for a Superhuman Docs (Coda) document. Before a doc reaches a reader, run the QA checklist, choose the interaction mode, set the publish frame, and confirm the share. Catches the broken formula, the wall of text, the orphaned bullet, the missing cover, the wrong audience. Trigger on "is this doc ready to share", "publish this doc", "QA this doc", "ship-check", "final pass before I send", "which interaction mode", or any moment a Superhuman Doc is about to leave the building.

Expert in creating opening lines, thumbnails, and hooks that stop the scroll. Covers curiosity gaps, pattern interrupts, emotional triggers, and platform-specific hooks. Knows how to earn attention in the first 3 seconds without resorting to clickbait. Use when "hook, opening line, scroll stopper, headline, first line, attention grab, thumbnail, clickable, " mentioned.

Pre-Merge Brief

Evaluates a local pre-trade checklist before manual order entry, blocking planless, oversized, revenge-risk, market-regime-blocked, or circuit-breaker-blocked entries while journaling the decision for later review.

Walk into the negotiation with a plan, not a hope. Sets your walk-away and your target, builds the concession ladder (what you trade and what you get for it), maps their likely asks, and drafts the responses that protect price and terms. Built for B2B sales teams, customizable to your CRM and your deal process. Trigger on "prep me for this negotiation", "the prospect wants a discount", "what should I concede", "build my concession ladder", "hold price on a new deal", or any pre-negotiation planning.

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Generates at most one token recommendation and one prediction-market pick per run, each with a falsifiable thesis, entry, sizing, and kill criterion. Returns NO_PICK when no candidate meets the bar.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Load this skill when the user says "prepare base", "prepare-base", or "/prepare-base". Prunes remote tracking references, checks out a base branch, pulls latest, and cleans up local-only feature branches after confirmation.

Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.

Automatically stages and commits all changes after a Spec Kit command completes, using configurable event-based hooks.

在启动一个重要项目或关键行动之前，用于主动识别和防范风险

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

Internal technical readiness drill assistant for release and handoff.

Enforces a mandatory pre-commit/pre-PR testing gate: detects the test stack, runs the full suite, fixes failures, creates minimal tests when none exist, and verifies coverage before allowing commits.

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

Use only for video game projects; define the emotional promise, player fantasy, vibe references, and hook

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Hero Recruiter

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.

Linting, formatting, and encoding standards for the AegisNex codebase. Covers ruff, mypy, eslint, editorconfig, pre-commit hooks, and how to add new quality checks.