Skip to content

jaktestowac/awesome-copilot-for-testers / plugins/creating-hooks/skills/creating-hooks

creating-hooks

Verified

Creates GitHub Copilot hooks for VS Code using `hooks.json`, supporting scripts, and companion docs. Use when automating deterministic checks, pre/post tool policies, or reusable hook packs that need safe defaults, observability, and clear installation guidance.

resources/hook-template-pack.md

View on GitHub
# Hook Template Pack

Use this pack as a starting point for a documented GitHub Copilot hook.
Replace placeholders, remove sections that do not apply, and keep the policy as small as possible.

## `README.md`

```md
# <Hook Title>

This hook <what it does> and is designed for <when or why it should run>.

## Behavior

- Event: `<preToolUse | postToolUse | ...>`
- Mode: `<observe | warn | deny | mutate>`
- Timeout: `<seconds>`
- Default action when uncertain: `<allow | deny>`

## Installation

- Copy this folder to `.github/hooks/<hook-name>/`
- Update the script names if you are only supporting one platform
- Review the patterns and messages before enabling blocking behavior

## Notes

- Explain what users should do if the hook denies an action
- Document any prerequisites such as `jq`, Node.js, or Python
- Mention limitations or known false positives
```

## `hooks.json`

```json
{
  "version": 1,
  "hooks": {
    "preToolUse": [
      {
        "type": "command",
        "command": "bash scripts/<hook-script>.sh",
        "windows": "powershell -File scripts\\<hook-script>.ps1",
        "cwd": ".github/hooks/<hook-name>",
        "timeoutSec": 10,
        "comment": "<Short explanation of the hook>"
      }
    ]
  }
}
```

## `scripts/<hook-script>.ps1`

```powershell
$inputObject = [Console]::In.ReadToEnd() | ConvertFrom-Json

# Extract the fields you care about from the hook payload.
$toolName = $inputObject.toolName
$toolArgs = $inputObject.toolArgs

# Evaluate your policy here.
$shouldDeny = $false
$reason = 'Replace with a user-friendly reason.'

if ($shouldDeny) {
  @{ permissionDecision = 'deny'; permissionDecisionReason = $reason } |
    ConvertTo-Json -Compress
}
```

## `scripts/<hook-script>.sh`

```bash
#!/usr/bin/env bash
set -euo pipefail

payload="$(cat)"

# Parse the fields you need. Adjust for your environment and dependencies.
tool_name="$(printf '%s' "$payload" | jq -r '.toolName')"

should_deny="false"
reason="Replace with a user-friendly reason."

if [ "$should_deny" = "true" ]; then
  printf '{"permissionDecision":"deny","permissionDecisionReason":"%s"}\n' "$reason"
fi
```

## Usage Notes

- Start with logging-only or warning behavior before introducing hard blocks.
- Keep scripts short and deterministic.
- Make denial reasons specific enough that users know what to change.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall