Codenotify
Adds the user's GitHub handle to the .github/CODENOTIFY file, mapping their contributions from git b
by microsoft · MIT
The skill
Adds the user's GitHub handle to the .github/CODENOTIFY file, mapping their contributions from git blame history to file and directory patterns (e.g. path/to/file.ts @handle, path/to/dir/** @handle) under the matching existing sections. Use when the user asks to add themselves to CODENOTIFY, register code ownership or notification entries, or update CODENOTIFY from git blame.
Add My Contributions to CODENOTIFY
This prompt helps you add your code contributions to the .github/CODENOTIFY file based on git blame history.
Instructions
Before running this prompt, provide the following information:
- Your GitHub handle: (e.g.,
@YOURHANDLE) - Alternative usernames in git blame: (e.g.,
Erich Gamma,ALIAS@microsoft.com, or any other names/emails that might appear in git commits)
What This Prompt Does
This prompt will:
- Search through the repository's git blame history for files you've significantly contributed to
- Analyze which files and directories have your contributions
- Follow the existing structure in the
.github/CODENOTIFYfile, here are some examples:src/vs/base/common/**→ Add to Base Utilities sectionsrc/vs/base/browser/ui/**→ Add to Base Widgets sectionsrc/vs/base/parts/**→ Add to Base Utilities sectionsrc/vs/platform/**→ Add to Platform sectionsrc/bootstrap-*.ts,src/main.ts, etc. → Add to Bootstrap sectionsrc/vs/code/**→ Add to Electron Main sectionsrc/vs/workbench/services/**→ Add to Workbench Services sectionsrc/vs/workbench/common/**,src/vs/workbench/browser/**→ Add to Workbench Core sectionsrc/vs/workbench/contrib/**→ Add to Workbench Contributions sectionsrc/vs/workbench/api/**→ Add to Workbench API sectionextensions/**→ Add to Extensions section
- Add appropriate entries in the format:
- Individual files:
path/to/file.ts @yourusername - Directories:
path/to/directory/** @yourusername
- Individual files:
- Place entries within existing sections, maintaining alphabetical or logical order
- Create new sections only if contributions don't fit existing categories
- Avoid duplicating existing entries
Expected Output Format
Entries will be added to existing sections based on their path. For example:
# Base Utilities
src/vs/base/common/extpath.ts @bpasero
src/vs/base/common/oauth.ts @yourusername # ← Your contribution added here
src/vs/base/parts/quickinput/** @yourusername # ← Your contribution added here
# Platform
src/vs/platform/quickinput/** @yourusername # ← Your contribution added here
src/vs/platform/secrets/** @yourusername # ← Your contribution added here
# Workbench Services
src/vs/workbench/services/authentication/** @yourusername # ← Your contribution added here
# Workbench Contributions
src/vs/workbench/contrib/authentication/** @yourusername # ← Your contribution added here
src/vs/workbench/contrib/localization/** @yourusername # ← Your contribution added here
If you have contributions that don't fit existing sections (e.g., foo/bar/**), new sections can be created at the end:
# Foo Bar
foo/bar/baz/** @yourusername
foo/bar/biz/** @yourusername
Notes
- CRITICAL: Entries must be added to the appropriate existing section based on their path
- Respect the existing organizational structure of the CODENOTIFY file
- If you're already listed for certain files/directories, those won't be duplicated
- Use
**wildcard for directories where you've touched multiple files - Maintain alphabetical or logical order within each section
Now, provide your GitHub handle and any alternative usernames found in git blame, and I'll help you update the CODENOTIFY file.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: microsoft/codenotify-12910132658.
Details
- Publisher
- microsoft
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-10-19
References
More from microsoft
- Chat Mode Authoring Author Copilot chat modes and instructions
- Azure Reliability Harden Azure workloads for availability
- Aks Gpu Inference Diagnose Day-2 AKS GPU and KAITO incidents using profile-aware, read-only evidence.
- Aks Known Issues Lookup documented AKS fixes only when the prompt includes an exact catalog signature and all of i…