Add weekly-demo-video and weekly-report Copilot skills#8099
Add weekly-demo-video and weekly-report Copilot skills#8099rajeshkamal5050 wants to merge 5 commits intomainfrom
Conversation
Adds Copilot CLI skills for automated weekly workflows: - weekly-demo-video: generates narrated MP4 demo videos - weekly-report: generates weekly feature summaries for LT Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
🔗 Linked Issue RequiredThanks for the contribution! Please link a GitHub issue to this PR by adding |
There was a problem hiding this comment.
Pull request overview
Adds two new Copilot CLI workflow skills under .github/skills/ to standardize (1) a weekly narrated demo-video pipeline and (2) a weekly executive status report workflow for the azd team.
Changes:
- Add
weekly-demo-videoskill and its detailed video-style/pipeline conventions reference. - Add
weekly-reportskill plus reference docs for section structure and tone rules.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
.github/skills/weekly-demo-video/SKILL.md |
Defines the weekly demo video workflow and steps to generate narrated MP4 demos. |
.github/skills/weekly-demo-video/references/CONVENTIONS.md |
Captures the rendering, audio, palette, font, and slide-type conventions for consistent videos. |
.github/skills/weekly-report/SKILL.md |
Defines the weekly exec report workflow (data gathering, changelog review, iteration loop). |
.github/skills/weekly-report/references/SECTION-RULES.md |
Defines strict per-section formatting/content rules for the report. |
.github/skills/weekly-report/references/TONE-RULES.md |
Defines tone/style constraints and common iteration patterns for report edits. |
wbreza
left a comment
There was a problem hiding this comment.
📝 Code Review — PR #8099
Add weekly-demo-video and weekly-report Copilot skills
🔴 P1 — Must Fix
1. CI Failing — No linked GitHub issue
📍 PR description
The pr-governance check is failing. Add Fixes #XXXX to the PR description or link an issue via the sidebar. This is a hard merge gate.
2. macOS-only install instructions
📍 weekly-demo-video/SKILL.md — Prerequisites table
Install commands use brew install exclusively, but this repo is actively developed on Windows (the skill itself includes Windows font paths). Add winget/choco alternatives for Windows and apt for Linux, or replace with a generic "Ensure Python 3, Pillow, ffmpeg, and edge-tts are installed."
🟡 P2 — Should Fix
3. No error handling guidance for video generation pipeline
📍 weekly-demo-video/SKILL.md — Step 5
The pipeline chains Python → edge-tts → ffmpeg with no recovery guidance. What should the agent do if edge-tts fails (rate limits, network) or ffmpeg errors on a slide? Add a brief error handling section.
4. Undocumented dependency on changelog-generation skill
📍 weekly-report/SKILL.md — Step 3
The weekly-report reads from changelog files that the changelog-generation skill writes. This implicit dependency should be documented (e.g., "Changelog data is maintained by the changelog-generation skill.").
5. Undefined "session files directory" output location
📍 weekly-report/SKILL.md — Output section
"Save reports to the session files directory" — but this is never defined. An AI agent won't know where to save. Reference the session workspace path or clarify the intended output location.
6. Missing INVOKES: line in frontmatter descriptions
📍 Both SKILL.md files
Existing skills (changelog-generation, azd-preflight, sensei) include an INVOKES: line listing tools/agents. Both new skills omit this. Add:
weekly-demo-video:INVOKES: Python, Pillow, ffmpeg, edge-tts, explore sub-agents, ask_user.weekly-report:INVOKES: gh CLI, git CLI, explore sub-agents, ask_user.
🟢 P3 — Suggestions
7. Strengthen anti-trigger references — Existing skills reference specific alternatives in DO NOT USE FOR: (e.g., "creating PRs (use pull-request)"). Consider adding: weekly-report: "release changelogs (use changelog-generation), daily standup (use standup-report)".
8. Add concrete date range example — The YYYY-MM-DD placeholders in weekly-report Step 2 would benefit from a real example showing the Thursday-to-Thursday cadence.
9. Consider adding license and metadata.version fields — Some existing skills include these; adding them to new skills would be good hygiene.
✅ What Looks Good
- No skill overlap conflicts — trigger phrases are distinct, no routing ambiguity
- Reference files are well-structured and follow established
references/patterns - Changelog paths verified — all three referenced files exist
- Tone rules reflect real iteration (9+ weeks) — prescriptive but effective
- Video conventions are comprehensive (color palette, fonts, slide types, ffmpeg pipeline)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add license: MIT and metadata.version to both skill frontmatters - Add INVOKES: line to both descriptions - Make install instructions cross-platform (generic) - Add prerequisites (gh, jq) to weekly-report - Add error handling section to weekly-demo-video - Document changelog-generation skill dependency - Define session workspace output path for weekly-report - Strengthen anti-trigger references in DO NOT USE FOR - Add concrete date range examples - Remove TONE-RULES.md and its reference Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
All review feedback addressed in commit 4052e51:
Also added |
Fixes #8033
Adds two Copilot CLI skills for automated weekly workflows:
weekly-demo-video
Generates narrated MP4 demo videos for azd features using Python + Pillow + edge-tts + ffmpeg. Includes full pipeline conventions, color palette, slide type specs, and cross-platform font support.
weekly-report
Generates weekly executive reports for LT. Includes section rules and iteration workflow.
Files
.github/skills/weekly-demo-video/SKILL.md— demo video workflow.github/skills/weekly-demo-video/references/CONVENTIONS.md— video style rules.github/skills/weekly-report/SKILL.md— report workflow.github/skills/weekly-report/references/SECTION-RULES.md— section format rules