codenotify

$npx mdskill add microsoft/vscode/codenotify

This prompt helps you add your code contributions to the `.github/CODENOTIFY` file based on git blame history.

SKILL.md

.github/skills/codenotifyView on GitHub ↗
---
name: codenotify
description: codenotify
disable-model-invocation: true
---
# 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:**

1. **Your GitHub handle:** (e.g., `@YOURHANDLE`)
2. **Alternative usernames in git blame:** (e.g., `Erich Gamma`, `[email protected]`, or any other names/emails that might appear in git commits)

## What This Prompt Does

This prompt will:
1. Search through the repository's git blame history for files you've significantly contributed to
2. Analyze which files and directories have your contributions
3. **Follow the existing structure** in the `.github/CODENOTIFY` file, here are some examples:
   - `src/vs/base/common/**` → Add to **Base Utilities** section
   - `src/vs/base/browser/ui/**` → Add to **Base Widgets** section
   - `src/vs/base/parts/**` → Add to **Base Utilities** section
   - `src/vs/platform/**` → Add to **Platform** section
   - `src/bootstrap-*.ts`, `src/main.ts`, etc. → Add to **Bootstrap** section
   - `src/vs/code/**` → Add to **Electron Main** section
   - `src/vs/workbench/services/**` → Add to **Workbench Services** section
   - `src/vs/workbench/common/**`, `src/vs/workbench/browser/**` → Add to **Workbench Core** section
   - `src/vs/workbench/contrib/**` → Add to **Workbench Contributions** section
   - `src/vs/workbench/api/**` → Add to **Workbench API** section
   - `extensions/**` → Add to **Extensions** section
4. Add appropriate entries in the format:
   - Individual files: `path/to/file.ts @yourusername`
   - Directories: `path/to/directory/** @yourusername`
5. Place entries within existing sections, maintaining alphabetical or logical order
6. Create new sections only if contributions don't fit existing categories
7. 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.**

More from microsoft/vscode

SkillDescription
accessibilityPrimary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
act-on-feedbackAct on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
agent-customization**WORKFLOW SKILL** — Create, update, review, fix, or debug VS Code agent customization files (.instructions.md, .prompt.md, .agent.md, SKILL.md, copilot-instructions.md, AGENTS.md). USE FOR: saving coding preferences; troubleshooting why instructions/skills/agents are ignored or not invoked; configuring applyTo patterns; defining tool restrictions; creating custom agent modes or specialized workflows; packaging domain knowledge; fixing YAML frontmatter syntax. DO NOT USE FOR: general coding questions (use default agent); runtime debugging or error diagnosis; MCP server configuration (use MCP docs directly); VS Code extension development. INVOKES: file system tools (read/write customization files), ask-questions tool (interview user for requirements), subagents for codebase exploration. FOR SINGLE OPERATIONS: For quick YAML frontmatter fixes or creating a single file from a known pattern, edit the file directly — no skill needed.
agent-host-chat-contributionsBuild and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
agent-host-e2e-testsUse when writing, recording, updating, validating, or troubleshooting Agent Host end-to-end and real-provider integration tests under src/vs/platform/agentHost/test/node/e2e and providerIntegration. Covers adding a cross-provider test, re-recording fixtures after an SDK bump, required cross-platform Azure validation, gating non-deterministic or platform-specific tests, and diagnosing replay cache misses.
agent-host-logsAnalyze Agent Host debug log exports. Use when given an ah-logs or ahp-logs zip/folder, an Export Agent Host Debug Logs bundle, events.jsonl, AHP JSONL transport logs, Agent Host.log, remote-agenthost.log, or copilot-logs.
author-contributionsIdentify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
auto-perf-optimizeRun agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
azure-pipelinesUse when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
build-champ-triageFind out why a build has failed