Add TLC meeting minutes skill#2676
Merged
Merged
Conversation
✅ Deploy Preview for selenium-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
diemol
approved these changes
Jul 16, 2026
titusfortner
marked this pull request as ready for review
July 16, 2026 15:24
Contributor
PR Summary by QodoAdd TLC meeting-minutes agent skill and publish 2026 TLC minutes
AI Description
Diagram
High-Level Assessment
Files changed (7)
|
Contributor
Code Review by Qodo
1. Unclear skill discovery paths
|
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
Comment on lines
+21
to
+22
| - Shared project skills live in `.agents/skills/`; inspect relevant `*/SKILL.md` files before | ||
| doing repeated or domain-specific workflows. |
Contributor
There was a problem hiding this comment.
1. Unclear skill discovery paths 🐞 Bug ⚙ Maintainability
AGENTS.md adds guidance to inspect .agents/skills/, but it does not clarify how this relates to the already-documented committed skills under scripts/skills/, leaving contributors/agents unsure which directories are authoritative for discovery and where new shared skills should be added.
Agent Prompt
## Issue description
`AGENTS.md` now mentions shared skills under `.agents/skills/`, but the document already defines `scripts/skills/` as the location for committed repo skills. Without explicitly stating the relationship (e.g., “inspect both”, “`.agents/skills` supersedes `scripts/skills`”, or “they serve different purposes”), skill discovery and future contributions are likely to be inconsistent.
## Issue Context
- The repo already contains a committed skill under `scripts/skills/`.
- This PR introduces a new committed skill under `.agents/skills/`.
## Fix Focus Areas
- AGENTS.md[19-29]
- scripts/skills/release-blog-post/SKILL.md[1-6]
- .agents/skills/tlc-meeting/SKILL.md[1-12]
## Suggested fix
- Update `AGENTS.md` to explicitly define:
- whether agents/contributors should inspect **both** `.agents/skills/` and `scripts/skills/`.
- which directory is the preferred destination for **new** shared skills.
- (optional) if one directory is legacy, add a short migration note.
- Consider aligning by either moving the new skill into `scripts/skills/` or updating the “Project-defined skills” section to include `.agents/skills/` as a first-class location (so the doc reads as one coherent policy).
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a shared
.agents/skills/tlc-meetingskill for generating Selenium TLC meeting minutes from local transcripts, and documents shared project skill discovery inAGENTS.md.Also adds 2026 TLC meeting minutes for:
The skill treats the transcript as the source of truth, uses the rolling agenda only for matching dated agenda context and public links, and allows GitHub PR/issue bodies/comments only as public reference context.
Motivation and Context
This makes TLC meeting minute generation repeatable and reviewable for future meetings. The skill encodes the workflow, participant mapping, evidence rules, GitHub handle-link style, and section responsibilities so future minutes avoid private transcript links, agenda-only content, unsupported decisions, and duplicated summary/decision/discussion text.
Types of changes