hooks-manager

Automate Claude Code lifecycle hooks for secrets scanning, formatting, and audit logging.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill hooks-manager-khamel83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hooks-manager
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/hooks-manager
Command: npx skills add https://github.com/Khamel83/oneshot --skill hooks-manager-khamel83

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

Automates Claude Code lifecycle hook management to enforce security, formatting, and context awareness.

Core Features & Use Cases

  • Secrets scanning before tool use to block exposure of API keys and secrets.
  • Post-tool auto-formatting to enforce consistent style.
  • Audit logging of tool executions for traceability.
  • Session-context injection to supply project context across sessions.

Quick Start

Install the hook scripts into your Claude Code project and configure .claude/settings.json to enable them and start automating your workflow.

Frequently Asked Questions about hooks-manager

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

FAQPage Schema
How do I automate Claude Code hooks to scan for secrets before tool execution?

You can automate Claude Code hook management to enforce secrets scanning before tool use by installing hook scripts and configuring .claude/settings.json, blocking exposure of API keys during project workflows.

Can I auto-format files after edits using Claude Code lifecycle hooks?

Yes, post-tool auto-formatting is a Claude Code lifecycle hook that enforces consistent style by automatically applying formatting rules immediately after an edit operation completes.

What is session-context injection and how does it work with Claude Code workflows?

Session-context injection is a hook mechanism that supplies persistent project context across multiple Claude Code sessions, ensuring the automated workflow retains necessary environment awareness.

Do I need jq to set up audit logging for Claude Code tool executions?

Yes, jq is a required dependency to configure audit logging of tool executions, providing traceability for automated workflows by processing JSON data within the .claude/settings.json setup.

Does this hooks automation workflow require specific settings configuration?

Yes, the workflow requires a supported project setup with .claude/settings.json adjustments to enable hooks, and the SKILL.md frontmatter must declare available hooks to run the automation.

When should I not use automated hooks for Claude Code security scanning?

You should avoid automated hooks for security scanning if your project lacks a supported .claude/settings.json configuration structure, as the lifecycle management depends on this file to enforce rules.