claude-code-tutor 1.0.0

package/skills-fallback/cc-common-workflows-run-claude-on-a-schedule/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: cc-common-workflows-run-claude-on-a-schedule
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Run Claude on a schedule
+
+Suppose you want Claude to handle a task automatically on a recurring basis, like reviewing open PRs every morning, auditing dependencies weekly, or checking for CI failures overnight.
+
+Pick a scheduling option based on where you want the task to run:
+
+| Option                                                 | Where it runs                     | Best for                                                                                                      |
+| :----------------------------------------------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------------------ |
+| [Cloud scheduled tasks](/en/web-scheduled-tasks)       | Anthropic-managed infrastructure  | Tasks that should run even when your computer is off. Configure at [claude.ai/code](https://claude.ai/code).  |
+| [Desktop scheduled tasks](/en/desktop-scheduled-tasks) | Your machine, via the desktop app | Tasks that need direct access to local files, tools, or uncommitted changes.                                  |
+| [GitHub Actions](/en/github-actions)                   | Your CI pipeline                  | Tasks tied to repo events like opened PRs, or cron schedules that should live alongside your workflow config. |
+| [`/loop`](/en/scheduled-tasks)                         | The current CLI session           | Quick polling while a session is open. Tasks are cancelled when you exit.                                     |
+
+***

package/skills-fallback/cc-common-workflows-run-parallel-claude-code-sessions-with-git-worktrees/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: cc-common-workflows-run-parallel-claude-code-sessions-with-git-worktrees
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Run parallel Claude Code sessions with Git worktrees
+
+When working on multiple tasks at once, you need each Claude session to have its own copy of the codebase so changes don't collide. Git worktrees solve this by creating separate working directories that each have their own files and branch, while sharing the same repository history and remote connections. This means you can have Claude working on a feature in one worktree while fixing a bug in another, without either session interfering with the other.
+
+Use the `--worktree` (`-w`) flag to create an isolated worktree and start Claude in it. The value you pass becomes the worktree directory name and branch name:
+
+```bash theme={null}
+# Start Claude in a worktree named "feature-auth"
+# Creates .claude/worktrees/feature-auth/ with a new branch
+claude --worktree feature-auth
+
+# Start another session in a separate worktree
+claude --worktree bugfix-123
+```
+
+If you omit the name, Claude generates a random one automatically:
+
+```bash theme={null}
+# Auto-generates a name like "bright-running-fox"
+claude --worktree
+```
+
+Worktrees are created at `<repo>/.claude/worktrees/<name>` and branch from the default remote branch, which is where `origin/HEAD` points. The worktree branch is named `worktree-<name>`.
+
+The base branch is not configurable through a Claude Code flag or setting. `origin/HEAD` is a reference stored in your local `.git` directory that Git set once when you cloned. If the repository's default branch later changes on GitHub or GitLab, your local `origin/HEAD` keeps pointing at the old one, and worktrees will branch from there. To re-sync your local reference with whatever the remote currently considers its default:
+
+```bash theme={null}
+git remote set-head origin -a
+```
+
+This is a standard Git command that only updates your local `.git` directory. Nothing on the remote server changes. If you want worktrees to base off a specific branch rather than the remote's default, set it explicitly with `git remote set-head origin your-branch-name`.
+
+For full control over how worktrees are created, including choosing a different base per invocation, configure a [WorktreeCreate hook](/en/hooks#worktreecreate). The hook replaces Claude Code's default `git worktree` logic entirely, so you can fetch and branch from whatever ref you need.
+
+You can also ask Claude to "work in a worktree" or "start a worktree" during a session, and it will create one automatically.

package/skills-fallback/cc-common-workflows-understand-new-codebases/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: cc-common-workflows-understand-new-codebases
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Common workflows
+
+> Step-by-step guides for exploring codebases, fixing bugs, refactoring, testing, and other everyday tasks with Claude Code.
+
+This page covers practical workflows for everyday development: exploring unfamiliar code, debugging, refactoring, writing tests, creating PRs, and managing sessions. Each section includes example prompts you can adapt to your own projects. For higher-level patterns and tips, see [Best practices](/en/best-practices).
+
+## Understand new codebases
+
+### Get a quick codebase overview
+
+Suppose you've just joined a new project and need to understand its structure quickly.
+
+  <Step title="Start Claude Code">
+    ```bash  theme={null}
+    claude 
+    ```
+  </Step>
+
+  <Step title="Ask for a high-level overview">
+    ```text  theme={null}
+    give me an overview of this codebase
+    ```
+  </Step>
+
+  <Step title="Dive deeper into specific components">
+    ```text  theme={null}
+    explain the main architecture patterns used here
+    ```
+
+````
+```text  theme={null}
+what are the key data models?
+```
+
+```text  theme={null}
+how is authentication handled?
+```
+````
+
+  </Step>
+</Steps>
+
+- Start with broad questions, then narrow down to specific areas
+- Ask about coding conventions and patterns used in the project
+- Request a glossary of project-specific terms
+
+### Find relevant code
+
+Suppose you need to locate code related to a specific feature or functionality.
+
+  <Step title="Get context on how components interact">
+    ```text  theme={null}
+    how do these authentication files work together?
+    ```
+  </Step>
+
+  <Step title="Understand the execution flow">
+    ```text  theme={null}
+    trace the login process from front-end to database
+    ```
+  </Step>
+</Steps>
+
+- Be specific about what you're looking for
+- Use domain language from the project
+- Install a [code intelligence plugin](/en/discover-plugins#code-intelligence) for your language to give Claude precise "go to definition" and "find references" navigation
+
+***

package/skills-fallback/cc-common-workflows-use-claude-as-a-unix-style-utility/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: cc-common-workflows-use-claude-as-a-unix-style-utility
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Use Claude as a unix-style utility
+
+### Add Claude to your verification process
+
+Suppose you want to use Claude Code as a linter or code reviewer.
+
+**Add Claude to your build script:**
+
+```json theme={null}
+// package.json
+{
+    ...
+    "scripts": {
+        ...
+        "lint:claude": "claude -p 'you are a linter. please look at the changes vs. main and report any issues related to typos. report the filename and line number on one line, and a description of the issue on the second line. do not return any other text.'"
+    }
+}
+```
+
+- Use Claude for automated code review in your CI/CD pipeline
+- Customize the prompt to check for specific issues relevant to your project
+- Consider creating multiple scripts for different types of verification
+
+### Pipe in, pipe out
+
+Suppose you want to pipe data into Claude, and get back data in a structured format.
+
+**Pipe data through Claude:**
+
+```bash theme={null}
+cat build-error.txt | claude -p 'concisely explain the root cause of this build error' > output.txt
+```
+
+- Use pipes to integrate Claude into existing shell scripts
+- Combine with other Unix tools for powerful workflows
+- Consider using `--output-format` for structured output
+
+### Control output format
+
+Suppose you need Claude's output in a specific format, especially when integrating Claude Code into scripts or other tools.
+
+```
+This outputs just Claude's plain text response (default behavior).
+```
+
+  </Step>
+
+  <Step title="Use JSON format">
+    ```bash  theme={null}
+    cat code.py | claude -p 'analyze this code for bugs' --output-format json > analysis.json
+    ```
+
+```
+This outputs a JSON array of messages with metadata including cost and duration.
+```
+
+  </Step>
+
+  <Step title="Use streaming JSON format">
+    ```bash  theme={null}
+    cat log.txt | claude -p 'parse this log file for errors' --output-format stream-json
+    ```
+
+```
+This outputs a series of JSON objects in real-time as Claude processes the request. Each message is a valid JSON object, but the entire output is not valid JSON if concatenated.
+```
+
+  </Step>
+</Steps>
+
+- Use `--output-format text` for simple integrations where you just need Claude's response
+- Use `--output-format json` when you need the full conversation log
+- Use `--output-format stream-json` for real-time output of each conversation turn
+
+***

package/skills-fallback/cc-common-workflows-use-extended-thinking-thinking-mode/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: cc-common-workflows-use-extended-thinking-thinking-mode
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Use extended thinking (thinking mode)
+
+[Extended thinking](https://platform.claude.com/docs/en/build-with-claude/extended-thinking) is enabled by default, giving Claude space to reason through complex problems step-by-step before responding. This reasoning is visible in verbose mode, which you can toggle on with `Ctrl+O`.
+
+Additionally, Opus 4.6 and Sonnet 4.6 support adaptive reasoning: instead of a fixed thinking token budget, the model dynamically allocates thinking based on your [effort level](/en/model-config#adjust-effort-level) setting. Extended thinking and adaptive reasoning work together to give you control over how deeply Claude reasons before responding.
+
+Extended thinking is particularly valuable for complex architectural decisions, challenging bugs, multi-step implementation planning, and evaluating tradeoffs between different approaches.

package/skills-fallback/cc-common-workflows-use-plan-mode-for-safe-code-analysis/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: cc-common-workflows-use-plan-mode-for-safe-code-analysis
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Use Plan Mode for safe code analysis
+
+Plan Mode instructs Claude to create a plan by analyzing the codebase with read-only operations, perfect for exploring codebases, planning complex changes, or reviewing code safely. In Plan Mode, Claude uses [`AskUserQuestion`](/en/tools-reference) to gather requirements and clarify your goals before proposing a plan.
+
+### When to use Plan Mode
+
+- **Multi-step implementation**: When your feature requires making edits to many files
+- **Code exploration**: When you want to research the codebase thoroughly before changing anything
+- **Interactive development**: When you want to iterate on the direction with Claude
+
+### How to use Plan Mode
+
+**Turn on Plan Mode during a session**
+
+You can switch into Plan Mode during a session using **Shift+Tab** to cycle through permission modes.
+
+If you are in Normal Mode, **Shift+Tab** first switches into Auto-Accept Mode, indicated by `⏵⏵ accept edits on` at the bottom of the terminal. A subsequent **Shift+Tab** will switch into Plan Mode, indicated by `⏸ plan mode on`.
+
+**Start a new session in Plan Mode**
+
+To start a new session in Plan Mode, use the `--permission-mode plan` flag:
+
+```bash theme={null}
+claude --permission-mode plan
+```
+
+**Run "headless" queries in Plan Mode**
+
+You can also run a query in Plan Mode directly with `-p` (that is, in ["headless mode"](/en/headless)):
+
+```bash theme={null}
+claude --permission-mode plan -p "Analyze the authentication system and suggest improvements"
+```
+
+### Example: Planning a complex refactor
+
+```bash theme={null}
+claude --permission-mode plan
+```
+
+```text theme={null}
+I need to refactor our authentication system to use OAuth2. Create a detailed migration plan.
+```
+
+Claude analyzes the current implementation and create a comprehensive plan. Refine with follow-ups:
+
+```text theme={null}
+What about backward compatibility?
+```
+
+```text theme={null}
+How should we handle database migration?
+```
+
+Press `Ctrl+G` to open the plan in your default text editor, where you can edit it directly before Claude proceeds.
+
+When you accept a plan, Claude automatically names the session from the plan content. The name appears on the prompt bar and in the session picker. If you've already set a name with `--name` or `/rename`, accepting a plan won't overwrite it.
+
+### Configure Plan Mode as default
+
+```json theme={null}
+// .claude/settings.json
+{
+  "permissions": {
+    "defaultMode": "plan"
+  }
+}
+```
+
+See [settings documentation](/en/settings#available-settings) for more configuration options.
+
+***

package/skills-fallback/cc-common-workflows-use-specialized-subagents/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: cc-common-workflows-use-specialized-subagents
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Use specialized subagents
+
+Suppose you want to use specialized AI subagents to handle specific tasks more effectively.
+
+```
+This shows all available subagents and lets you create new ones.
+```
+
+  </Step>
+
+  <Step title="Use subagents automatically">
+    Claude Code automatically delegates appropriate tasks to specialized subagents:
+
+````
+```text  theme={null}
+review my recent code changes for security issues
+```
+
+```text  theme={null}
+run all tests and fix any failures
+```
+````
+
+  </Step>
+
+  <Step title="Explicitly request specific subagents">
+    ```text  theme={null}
+    use the code-reviewer subagent to check the auth module
+    ```
+
+````
+```text  theme={null}
+have the debugger subagent investigate why users can't log in
+```
+````
+
+  </Step>
+
+  <Step title="Create custom subagents for your workflow">
+    ```text  theme={null}
+    /agents
+    ```
+
+```
+Then select "Create New subagent" and follow the prompts to define:
+
+* A unique identifier that describes the subagent's purpose (for example, `code-reviewer`, `api-designer`).
+* When Claude should use this agent
+* Which tools it can access
+* A system prompt describing the agent's role and behavior
+```
+
+  </Step>
+</Steps>
+
+- Create project-specific subagents in `.claude/agents/` for team sharing
+- Use descriptive `description` fields to enable automatic delegation
+- Limit tool access to what each subagent actually needs
+- Check the [subagents documentation](/en/sub-agents) for detailed examples
+
+***

package/skills-fallback/cc-common-workflows-work-with-images/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: cc-common-workflows-work-with-images
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Work with images
+
+Suppose you need to work with images in your codebase, and you want Claude's help analyzing image content.
+
+```
+1. Drag and drop an image into the Claude Code window
+2. Copy an image and paste it into the CLI with ctrl+v (Do not use cmd+v)
+3. Provide an image path to Claude. E.g., "Analyze this image: /path/to/your/image.png"
+```
+
+  </Step>
+
+  <Step title="Ask Claude to analyze the image">
+    ```text  theme={null}
+    What does this image show?
+    ```
+
+````
+```text  theme={null}
+Describe the UI elements in this screenshot
+```
+
+```text  theme={null}
+Are there any problematic elements in this diagram?
+```
+````
+
+  </Step>
+
+  <Step title="Use images for context">
+    ```text  theme={null}
+    Here's a screenshot of the error. What's causing it?
+    ```
+
+````
+```text  theme={null}
+This is our current database schema. How should we modify it for the new feature?
+```
+````
+
+  </Step>
+
+  <Step title="Get code suggestions from visual content">
+    ```text  theme={null}
+    Generate CSS to match this design mockup
+    ```
+
+````
+```text  theme={null}
+What HTML structure would recreate this component?
+```
+````
+
+  </Step>
+</Steps>
+
+- Use images when text descriptions would be unclear or cumbersome
+- Include screenshots of errors, UI designs, or diagrams for better context
+- You can work with multiple images in a conversation
+- Image analysis works with diagrams, screenshots, mockups, and more
+- When Claude references images (for example, `[Image #1]`), `Cmd+Click` (Mac) or `Ctrl+Click` (Windows/Linux) the link to open the image in your default viewer
+
+***

package/skills-fallback/cc-common-workflows-work-with-tests/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: cc-common-workflows-work-with-tests
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Work with tests
+
+Suppose you need to add tests for uncovered code.
+
+  <Step title="Generate test scaffolding">
+    ```text  theme={null}
+    add tests for the notification service
+    ```
+  </Step>
+
+  <Step title="Add meaningful test cases">
+    ```text  theme={null}
+    add test cases for edge conditions in the notification service
+    ```
+  </Step>
+
+  <Step title="Run and verify tests">
+    ```text  theme={null}
+    run the new tests and fix any failures
+    ```
+  </Step>
+</Steps>
+
+Claude can generate tests that follow your project's existing patterns and conventions. When asking for tests, be specific about what behavior you want to verify. Claude examines your existing test files to match the style, frameworks, and assertion patterns already in use.
+
+For comprehensive coverage, ask Claude to identify edge cases you might have missed. Claude can analyze your code paths and suggest tests for error conditions, boundary values, and unexpected inputs that are easy to overlook.
+
+***

package/skills-fallback/cc-github-actions/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: cc-github-actions
+description: "Claude Code en GitHub Actions: setup, @claude mentions, configuración con Bedrock y Vertex, security considerations."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/github-actions.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Claude Code GitHub Actions
+
+> Learn about integrating Claude Code into your development workflow with Claude Code GitHub Actions
+
+Claude Code GitHub Actions brings AI-powered automation to your GitHub workflow. With a simple `@claude` mention in any PR or issue, Claude can analyze your code, create pull requests, implement features, and fix bugs - all while following your project's standards. For automatic reviews posted on every PR without a trigger, see [GitHub Code Review](/en/code-review).
+
+## Why use Claude Code GitHub Actions?
+
+- **Instant PR creation**: Describe what you need, and Claude creates a complete PR with all necessary changes
+- **Automated code implementation**: Turn issues into working code with a single command
+- **Follows your standards**: Claude respects your `CLAUDE.md` guidelines and existing code patterns
+- **Simple setup**: Get started in minutes with our installer and API key
+- **Secure by default**: Your code stays on Github's runners
+
+## What can Claude do?
+
+Claude Code provides a powerful GitHub Action that transforms how you work with code:
+
+### Claude Code Action
+
+This GitHub Action allows you to run Claude Code within your GitHub Actions workflows. You can use this to build any custom workflow on top of Claude Code.
+
+[View repository →](https://github.com/anthropics/claude-code-action)
+
+## Setup
+
+## Quick setup
+
+The easiest way to set up this action is through Claude Code in the terminal. Just open claude and run `/install-github-app`.
+
+This command will guide you through setting up the GitHub app and required secrets.

package/skills-fallback/cc-headless/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: cc-headless
+description: "Modo headless y Agent SDK de Claude Code: uso programático desde CLI, Python y TypeScript, output estructurado, bare mode."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/headless.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Run Claude Code programmatically
+
+> Use the Agent SDK to run Claude Code programmatically from the CLI, Python, or TypeScript.
+
+The [Agent SDK](https://platform.claude.com/docs/en/agent-sdk/overview) gives you the same tools, agent loop, and context management that power Claude Code. It's available as a CLI for scripts and CI/CD, or as [Python](https://platform.claude.com/docs/en/agent-sdk/python) and [TypeScript](https://platform.claude.com/docs/en/agent-sdk/typescript) packages for full programmatic control.
+
+To run Claude Code programmatically from the CLI, pass `-p` with your prompt and any [CLI options](/en/cli-reference):
+
+```bash theme={null}
+claude -p "Find and fix the bug in auth.py" --allowedTools "Read,Edit,Bash"
+```
+
+This page covers using the Agent SDK via the CLI (`claude -p`). For the Python and TypeScript SDK packages with structured outputs, tool approval callbacks, and native message objects, see the [full Agent SDK documentation](https://platform.claude.com/docs/en/agent-sdk/overview).
+
+## Basic usage
+
+Add the `-p` (or `--print`) flag to any `claude` command to run it non-interactively. All [CLI options](/en/cli-reference) work with `-p`, including:
+
+- `--continue` for [continuing conversations](#continue-conversations)
+- `--allowedTools` for [auto-approving tools](#auto-approve-tools)
+- `--output-format` for [structured output](#get-structured-output)
+
+This example asks Claude a question about your codebase and prints the response:
+
+```bash theme={null}
+claude -p "What does the auth module do?"
+```

package/skills-fallback/cc-hooks-config/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: cc-hooks-config
+description: "Configuración de hooks en settings.json, matchers, campos"
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/hooks.md"
+---
+## Configuration
+
+Hooks are defined in JSON settings files. The configuration has three levels of nesting:
+
+1. Choose a [hook event](#hook-events) to respond to, like `PreToolUse` or `Stop`
+2. Add a [matcher group](#matcher-patterns) to filter when it fires, like "only for the Bash tool"
+3. Define one or more [hook handlers](#hook-handler-fields) to run when matched
+
+See [How a hook resolves](#how-a-hook-resolves) above for a complete walkthrough with an annotated example.
+
+### Hook locations
+
+Where you define a hook determines its scope:
+
+| Location                                                   | Scope                         | Shareable                          |
+| :--------------------------------------------------------- | :---------------------------- | :--------------------------------- |
+| `~/.claude/settings.json`                                  | All your projects             | No, local to your machine          |
+| `.claude/settings.json`                                    | Single project                | Yes, can be committed to the repo  |
+| `.claude/settings.local.json`                              | Single project                | No, gitignored                     |
+| Managed policy settings                                    | Organization-wide             | Yes, admin-controlled              |
+| [Plugin](/en/plugins) `hooks/hooks.json`                   | When plugin is enabled        | Yes, bundled with the plugin       |
+| [Skill](/en/skills) or [agent](/en/sub-agents) frontmatter | While the component is active | Yes, defined in the component file |
+
+For details on settings file resolution, see [settings](/en/settings). Enterprise administrators can use `allowManagedHooksOnly` to block user, project, and plugin hooks. See [Hook configuration](/en/settings#hook-configuration).

package/skills-fallback/cc-hooks-events/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: cc-hooks-events
+description: "Tabla de eventos y cuándo se disparan"
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/hooks.md"
+---
+## Hook lifecycle
+
+Hooks fire at specific points during a Claude Code session. When an event fires and a matcher matches, Claude Code passes JSON context about the event to your hook handler. For command hooks, input arrives on stdin. For HTTP hooks, it arrives as the POST request body. Your handler can then inspect the input, take action, and optionally return a decision. Some events fire once per session, while others fire repeatedly inside the agentic loop:
+
+<div style={{maxWidth: "500px", margin: "0 auto"}}>
+  <Frame>
+    <img src="https://mintcdn.com/claude-code/WLZtXlltXc8aIoIM/images/hooks-lifecycle.svg?fit=max&auto=format&n=WLZtXlltXc8aIoIM&q=85&s=6a0bf67eeb570a96e36b564721fa2a93" alt="Hook lifecycle diagram showing the sequence of hooks from SessionStart through the agentic loop (PreToolUse, PermissionRequest, PostToolUse, SubagentStart/Stop, TaskCreated, TaskCompleted) to Stop or StopFailure, TeammateIdle, PreCompact, PostCompact, and SessionEnd, with Elicitation and ElicitationResult nested inside MCP tool execution, PermissionDenied as a side branch from PermissionRequest for auto-mode denials, and WorktreeCreate, WorktreeRemove, Notification, ConfigChange, InstructionsLoaded, CwdChanged, and FileChanged as standalone async events" width="520" height="1155" data-path="images/hooks-lifecycle.svg" />
+  </Frame>
+</div>
+
+The table below summarizes when each event fires. The [Hook events](#hook-events) section documents the full input schema and decision control options for each one.
+
+| Event                | When it fires                                                                                                                                          |
+| :------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `SessionStart`       | When a session begins or resumes                                                                                                                       |
+| `UserPromptSubmit`   | When you submit a prompt, before Claude processes it                                                                                                   |