Initial shared Copilot resources scaffold

This commit is contained in:
2026-04-23 15:46:34 -04:00
commit adfcb83ab6
44 changed files with 2249 additions and 0 deletions

View File

@@ -0,0 +1,20 @@
---
name: "Resource Maintainer"
description: "Use when maintaining the shared Copilot resource repository, publishing local resources into the repo, or reviewing naming, portability, and propagation concerns."
tools: [read, search, edit, execute, todo]
model: "GPT-5 (copilot)"
---
You maintain the shared Copilot resource repository.
## Constraints
- Keep the repository authoritative for shared assets.
- Prefer small, reviewable changes.
- Validate scripts and config before finishing.
- Treat prompts as adapters and skills as the canonical portable workflow layer.
## Output
Summarize what changed, how it propagates, and any follow-up validation or
commit steps.

View File

@@ -0,0 +1,12 @@
{
"hooks": {
"SessionStart": [
{
"type": "command",
"osx": "~/.copilot-resources/resources/scripts/report-hook-event.sh",
"linux": "~/.copilot-resources/resources/scripts/report-hook-event.sh",
"windows": "powershell -NoProfile -File \"$HOME/.copilot-resources/resources/scripts/report-hook-event.ps1\""
}
]
}
}

View File

@@ -0,0 +1,12 @@
---
name: "Copilot Customization Standards"
description: "Use when authoring or editing shared Copilot prompts, instructions, agents, skills, hooks, or overlay templates. Covers naming, portability, and frontmatter expectations."
applyTo: "resources/prompts/**/*.prompt.md,resources/instructions/**/*.instructions.md,resources/agents/**/*.agent.md,resources/skills/**/SKILL.md,templates/repo-overlay/.github/instructions/**/*.instructions.md,templates/repo-overlay/.github/agents/**/*.agent.md"
---
- Prefer skills for portable workflows and prompts for VS Code-only adapters.
- Keep descriptions discovery-oriented: say what the resource does and when to
use it.
- Do not duplicate workflow logic across prompts and skills without a reason.
- Keep shared resources neutral and reusable rather than tied to one machine.
- Treat repository overlays as templates, not as the authoritative shared copy.

5
resources/mcp/README.md Normal file
View File

@@ -0,0 +1,5 @@
# MCP Notes
This folder is reserved for reusable MCP references and safe shared
configuration snippets. Machine-specific secrets and authenticated local server
definitions should stay out of the repository.

View File

@@ -0,0 +1,17 @@
---
name: "publish-resource"
description: "Publish a prompt, instruction, agent, hook, or skill into the shared Copilot resource repository."
agent: "agent"
tools: [read, search, edit, execute]
argument-hint: "source=<path> kind=<prompt|instruction|agent|hook|skill> name=<optional>"
---
Publish the resource into the shared repository by using the repository's
publish script.
Requirements:
- Detect or confirm the resource kind.
- Use the repository publish script instead of copying files manually.
- Review the normalized result.
- Summarize what changed and what should be committed.

View File

@@ -0,0 +1,8 @@
$ErrorActionPreference = 'Stop'
$StateDir = if ($env:COPILOT_RESOURCES_STATE_DIR) { $env:COPILOT_RESOURCES_STATE_DIR } else { Join-Path $HOME '.copilot-resources-state' }
New-Item -ItemType Directory -Path $StateDir -Force | Out-Null
$Payload = [Console]::In.ReadToEnd()
$Payload | Add-Content -LiteralPath (Join-Path $StateDir 'hook-events.log')
'{"continue": true}'

View File

@@ -0,0 +1,10 @@
#!/usr/bin/env bash
set -euo pipefail
state_dir="${COPILOT_RESOURCES_STATE_DIR:-$HOME/.copilot-resources-state}"
mkdir -p -- "$state_dir"
event_payload="$(cat)"
printf '%s\n' "$event_payload" >> "$state_dir/hook-events.log"
printf '{"continue": true}\n'

View File

@@ -0,0 +1,23 @@
---
name: resource-authoring
description: "Use when adding, publishing, or reviewing shared Copilot resources such as skills, prompts, instructions, agents, hooks, or supporting scripts."
argument-hint: "[resource type] [goal]"
---
# Resource Authoring
Use this skill when the task is to create or evolve a shared Copilot resource in
the repository.
## Procedure
1. Decide whether the resource should be a skill, prompt, agent, instruction,
or hook.
2. Prefer repo-first authoring when the work is intentionally shared.
3. If the resource originated elsewhere, publish it into the repository.
4. Review naming, portability, and lifecycle impact.
5. Validate any scripts or automation referenced by the resource.
## References
- [Publishing checklist](./references/publishing-checklist.md)

View File

@@ -0,0 +1,7 @@
# Publishing Checklist
- Choose the correct primitive.
- Confirm the target folder and filename.
- Confirm frontmatter is valid and descriptive.
- Avoid duplicating a workflow that already exists.
- If scripts are referenced, validate them before merging.

View File

@@ -0,0 +1,8 @@
# New Shared Resource Checklist
- Pick the correct primitive.
- Confirm the target location.
- Add clear frontmatter.
- Check naming and portability rules.
- Validate any referenced scripts.
- Commit and push after publishing.