Initial shared Copilot resources scaffold
This commit is contained in:
37
docs/publishing.md
Normal file
37
docs/publishing.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Publishing Guide
|
||||
|
||||
## Why Publishing Exists
|
||||
|
||||
VS Code creation flows can write to a workspace or user profile, but those
|
||||
locations are not the authoritative shared source. Publishing moves the resource
|
||||
into this repository so other sessions and machines can consume the same asset.
|
||||
|
||||
## Examples
|
||||
|
||||
```bash
|
||||
install/publish.sh --source /path/to/example.prompt.md
|
||||
```
|
||||
|
||||
```powershell
|
||||
install/publish.ps1 -Source C:\path\to\example.agent.md
|
||||
```
|
||||
|
||||
## What Publish Normalizes
|
||||
|
||||
- target filenames and skill directory names are normalized into lowercase
|
||||
kebab-case
|
||||
- expected suffixes are enforced for prompts, instructions, agents, and hooks
|
||||
- skill `name` metadata is aligned to the published directory name
|
||||
|
||||
## What Publish Rejects
|
||||
|
||||
- exact content duplicates that already exist elsewhere in the shared repo
|
||||
- effective display-name duplicates, even if the filenames differ
|
||||
- conflicting targets unless you explicitly replace them with `--force` or
|
||||
`-Force`
|
||||
|
||||
## After Publishing
|
||||
|
||||
1. Review the normalized target in this repository.
|
||||
2. Commit and push.
|
||||
3. Update other systems.
|
||||
Reference in New Issue
Block a user