Merge branch 'main' into main

Author: BethanyJep

AGENTS.md

@@ -8,6 +8,7 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
 - **Prompts** - Task-specific prompts for code generation and problem-solving
 - **Instructions** - Coding standards and best practices applied to specific file patterns
 - **Skills** - Self-contained folders with instructions and bundled resources for specialized tasks
+- **Hooks** - Automated workflows triggered by specific events during development
 - **Collections** - Curated collections organized around specific themes and workflows
 
 ## Repository Structure
@@ -18,6 +19,7 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
 ├── prompts/          # Task-specific prompts (.prompt.md files)
 ├── instructions/     # Coding standards and guidelines (.instructions.md files)
 ├── skills/           # Agent Skills folders (each with SKILL.md and optional bundled assets)
+├── hooks/            # Automated workflow hooks (folders with README.md + hooks.json)
 ├── collections/      # Curated collections of resources (.md files)
 ├── docs/             # Documentation for different resource types
 ├── eng/              # Build and automation scripts
@@ -48,9 +50,9 @@ npm run skill:create -- --name <skill-name>
 
 ## Development Workflow
 
-### Working with Agents, Prompts, Instructions, and Skills
+### Working with Agents, Prompts, Instructions, Skills, and Hooks
 
-All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets:
+All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets. Hooks are folders containing a `README.md` with frontmatter and a `hooks.json` configuration file:
 
 #### Agent Files (*.agent.md)
 - Must have `description` field (wrapped in single quotes)
@@ -80,16 +82,37 @@ All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction fi
 - Asset files should be reasonably sized (under 5MB per file)
 - Skills follow the [Agent Skills specification](https://agentskills.io/specification)
 
+#### Hook Folders (hooks/*/README.md)
+- Each hook is a folder containing a `README.md` file with frontmatter
+- README.md must have `name` field (human-readable name)
+- README.md must have `description` field (wrapped in single quotes, not empty)
+- Must include a `hooks.json` file with hook configuration (hook events extracted from this file)
+- Folder names should be lower case with words separated by hyphens
+- Can include bundled assets (scripts, utilities, configuration files)
+- Bundled scripts should be referenced in the README.md and hooks.json
+- Follow the [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
+- Optionally includes `tags` field for categorization
+
 ### Adding New Resources
 
-When adding a new agent, prompt, instruction, or skill:
+When adding a new agent, prompt, instruction, skill, or hook:
 
 **For Agents, Prompts, and Instructions:**
 1. Create the file with proper front matter
 2. Add the file to the appropriate directory
 3. Update the README.md by running: `npm run build`
 4. Verify the resource appears in the generated README
 
+**For Hooks:**
+1. Create a new folder in `hooks/` with a descriptive name
+2. Create `README.md` with proper frontmatter (name, description, hooks, tags)
+3. Create `hooks.json` with hook configuration following GitHub Copilot hooks spec
+4. Add any bundled scripts or assets to the folder
+5. Make scripts executable: `chmod +x script.sh`
+6. Update the README.md by running: `npm run build`
+7. Verify the hook appears in the generated README
+
+
 **For Skills:**
 1. Run `npm run skill:create` to scaffold a new skill folder
 2. Edit the generated SKILL.md file with your instructions
@@ -186,6 +209,16 @@ For skills (skills/*/):
 - [ ] Any bundled assets are referenced in SKILL.md
 - [ ] Bundled assets are under 5MB per file
 
+For hook folders (hooks/*/):
+- [ ] Folder contains a README.md file with markdown front matter
+- [ ] Has `name` field with human-readable name
+- [ ] Has non-empty `description` field wrapped in single quotes
+- [ ] Has `hooks.json` file with valid hook configuration (hook events extracted from this file)
+- [ ] Folder name is lower case with hyphens
+- [ ] Any bundled scripts are executable and referenced in README.md
+- [ ] Follows [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
+- [ ] Optionally includes `tags` array field for categorization
+
 ## Contributing
 
 This is a community-driven project. Contributions are welcome! Please see:

README.md

@@ -11,6 +11,7 @@ This repository provides a comprehensive toolkit for enhancing GitHub Copilot wi
 - **👉 [Awesome Agents](docs/README.agents.md)** - Specialized GitHub Copilot agents that integrate with MCP servers to provide enhanced capabilities for specific workflows and tools
 - **👉 [Awesome Prompts](docs/README.prompts.md)** - Focused, task-specific prompts for generating code, documentation, and solving specific problems
 - **👉 [Awesome Instructions](docs/README.instructions.md)** - Comprehensive coding standards and best practices that apply to specific file patterns or entire projects
+- **👉 [Awesome Hooks](docs/README.hooks.md)** - Automated workflows triggered by specific events during development, testing, and deployment
 - **👉 [Awesome Skills](docs/README.skills.md)** - Self-contained folders with instructions and bundled resources that enhance AI capabilities for specialized tasks
 - **👉 [Awesome Collections](docs/README.collections.md)** - Curated collections of related prompts, instructions, agents, and skills organized around specific themes and workflows
 - **👉 [Awesome Cookbook Recipes](cookbook/README.md)** - Practical, copy-paste-ready code snippets and real-world examples for working with GitHub Copilot tools and features
@@ -96,6 +97,10 @@ Use the `/` command in GitHub Copilot Chat to access prompts:
 
 Instructions automatically apply to files based on their patterns and provide contextual guidance for coding standards, frameworks, and best practices.
 
+### 🪝 Hooks
+
+Hooks enable automated workflows triggered by specific events during GitHub Copilot coding agent sessions (like sessionStart, sessionEnd, userPromptSubmitted). They can automate tasks like logging, auto-committing changes, or integrating with external services.
+
 ## 🎯 Why Use Awesome GitHub Copilot?
 
 - **Productivity**: Pre-built agents, prompts and instructions save time and provide consistent results.
@@ -107,7 +112,7 @@ Instructions automatically apply to files based on their patterns and provide co
 
 We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.md) for details on how to:
 
-- Add new prompts, instructions, agents, or skills
+- Add new prompts, instructions, hooks, agents, or skills
 - Improve existing content
 - Report issues or suggest enhancements
 
@@ -148,7 +153,7 @@ The customizations in this repository are sourced from and created by third-part
 
 ---
 
-**Ready to supercharge your coding experience?** Start exploring our [prompts](docs/README.prompts.md), [instructions](docs/README.instructions.md), and [custom agents](docs/README.agents.md)!
+**Ready to supercharge your coding experience?** Start exploring our [prompts](docs/README.prompts.md), [instructions](docs/README.instructions.md), [hooks](docs/README.hooks.md), and [custom agents](docs/README.agents.md)!
 
 ## Contributors ✨
 

agents/context-architect.agent.md

@@ -0,0 +1,60 @@
+---
+description: 'An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies'
+model: 'GPT-5'
+tools: ['codebase', 'terminalCommand']
+name: 'Context Architect'
+---
+
+You are a Context Architect—an expert at understanding codebases and planning changes that span multiple files.
+
+## Your Expertise
+
+- Identifying which files are relevant to a given task
+- Understanding dependency graphs and ripple effects
+- Planning coordinated changes across modules
+- Recognizing patterns and conventions in existing code
+
+## Your Approach
+
+Before making any changes, you always:
+
+1. **Map the context**: Identify all files that might be affected
+2. **Trace dependencies**: Find imports, exports, and type references
+3. **Check for patterns**: Look at similar existing code for conventions
+4. **Plan the sequence**: Determine the order changes should be made
+5. **Identify tests**: Find tests that cover the affected code
+
+## When Asked to Make a Change
+
+First, respond with a context map:
+
+```
+## Context Map for: [task description]
+
+### Primary Files (directly modified)
+- path/to/file.ts — [why it needs changes]
+
+### Secondary Files (may need updates)
+- path/to/related.ts — [relationship]
+
+### Test Coverage
+- path/to/test.ts — [what it tests]
+
+### Patterns to Follow
+- Reference: path/to/similar.ts — [what pattern to match]
+
+### Suggested Sequence
+1. [First change]
+2. [Second change]
+...
+```
+
+Then ask: "Should I proceed with this plan, or would you like me to examine any of these files first?"
+
+## Guidelines
+
+- Always search the codebase before assuming file locations
+- Prefer finding existing patterns over inventing new ones
+- Warn about breaking changes or ripple effects
+- If the scope is large, suggest breaking into smaller PRs
+- Never make changes without showing the context map first

agents/reepl-linkedin.agent.md

@@ -0,0 +1,42 @@
+---
+name: reepl-linkedin
+description: "AI-powered LinkedIn content creation, scheduling, and analytics agent. Create posts, carousels, and manage your LinkedIn presence with GitHub Copilot."
+---
+
+# Reepl -- LinkedIn Content Agent
+
+You are a LinkedIn content strategist and automation expert powered by [Reepl](https://reepl.io). You help developers, marketers, and professionals create, schedule, and analyze LinkedIn content directly from their editor.
+
+**What is Reepl?** Reepl is an AI-powered LinkedIn content management platform that lets you create posts, design carousels, schedule content, and track analytics. Learn more at [reepl.io](https://reepl.io) or explore the skills repository at [github.com/reepl-io/skills](https://github.com/reepl-io/skills).
+
+## Core Capabilities
+
+- **Post Creation:** Draft engaging LinkedIn posts with AI assistance, including text formatting, hashtag suggestions, and hook optimization.
+- **Carousel Design:** Generate multi-slide LinkedIn carousels with structured content and visual layouts.
+- **Content Scheduling:** Plan and schedule posts for optimal engagement times.
+- **Analytics:** Review post performance, engagement metrics, and audience insights.
+- **Voice Profiles:** Match content tone and style to a user's personal brand or voice profile.
+
+## Workflow
+
+1. **Understand the Goal:** Ask what the user wants to achieve -- thought leadership, product launch, hiring, community engagement, etc.
+2. **Draft Content:** Create LinkedIn-optimized content following best practices (hooks, formatting, CTAs).
+3. **Refine:** Iterate on tone, length, and structure based on feedback.
+4. **Schedule or Publish:** Help the user schedule or publish the content through Reepl.
+
+## LinkedIn Content Best Practices
+
+- Start with a strong hook in the first two lines to earn the "see more" click.
+- Use short paragraphs and line breaks for readability on mobile.
+- Include a clear call-to-action (comment, share, visit link).
+- Keep hashtags relevant and limited to 3-5 per post.
+- Carousels should tell a story with a clear beginning, middle, and end.
+- Optimal post length is 1,200-1,500 characters for engagement.
+
+## Guidelines
+
+- Always tailor content to the user's industry and audience.
+- Maintain a professional but authentic tone unless the user specifies otherwise.
+- Respect LinkedIn's content policies and community guidelines.
+- Never generate misleading, spammy, or engagement-bait content.
+- Prioritize value-driven content that educates, inspires, or informs.

collections/context-engineering.collection.yml

@@ -0,0 +1,60 @@
+id: context-engineering
+name: Context Engineering
+description: Tools and techniques for maximizing GitHub Copilot effectiveness through better context management. Includes guidelines for structuring code, an agent for planning multi-file changes, and prompts for context-aware development.
+tags: [context, productivity, refactoring, best-practices, architecture]
+
+items:
+  - path: instructions/context-engineering.instructions.md
+    kind: instruction
+
+  - path: agents/context-architect.agent.md
+    kind: agent
+    usage: |
+      recommended
+
+      The Context Architect agent helps plan multi-file changes by mapping dependencies
+      and identifying all relevant files before making modifications.
+
+      Use this agent when:
+      - Planning refactors that span multiple files
+      - Adding features that touch several modules
+      - Investigating unfamiliar parts of the codebase
+
+      Example usage:
+      ```
+      @context-architect I need to add rate limiting to all API endpoints.
+      What files are involved and what's the best approach?
+      ```
+
+      For best results:
+      - Describe the high-level goal, not just the immediate task
+      - Let the agent search before you provide files
+      - Review the context map before approving changes
+
+  - path: prompts/context-map.prompt.md
+    kind: prompt
+    usage: |
+      optional
+
+      Use before any significant change to understand the blast radius.
+      Produces a structured map of files, dependencies, and tests.
+
+  - path: prompts/what-context-needed.prompt.md
+    kind: prompt
+    usage: |
+      optional
+
+      Use when Copilot gives a generic or incorrect answer.
+      Asks Copilot to explicitly list what files it needs to see.
+
+  - path: prompts/refactor-plan.prompt.md
+    kind: prompt
+    usage: |
+      optional
+
+      Use for multi-file refactors. Produces a phased plan with
+      verification steps and rollback procedures.
+
+display:
+  ordering: manual
+  show_badge: true