Results for “pre-tool-hook”

Blocks Edit/Write/Bash actions until the agent presents concrete facts about imports, data schemas, and the user's instruction, improving output quality.

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.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Research existing tools, libraries, and patterns before writing custom code by invoking a researcher agent.

Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.

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.

研究优先于编码的工作流程。在编写自定义代码之前，搜索现有的工具、库和模式。调用研究员代理。

Internal technical readiness drill assistant for release and handoff.

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.

Guides a research-before-coding workflow, searching existing tools, libraries, and patterns before writing custom code, with decision matrices and integration with agent workflows.

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

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

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".

Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.

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.

Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.

Self-evolution and contribution system for makepad-skills. Use when capturing new patterns, correcting skill errors, contributing learnings, or setting up hooks for auto-triggered skill updates.

Forces AI agents to investigate before editing or running destructive commands, improving code quality by requiring concrete facts like importers, data schemas, and user instructions.