ProfessorGPTProfessorGPT
Microsoft
MicrosoftMicrosoft· v1.0.0
analysisOfficial
Official Provider SkillView repo

Your memory store: overview, list, review, forget, edit, help.

Files2 files
SKILL.md303 lines
Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select an AI agent above to see the install command.

or

Manual Install

More steps

Download the archive and add the files to your project manually.

Skill details

Versionv1.0.0
AuthorMicrosoft
Categoryanalysis
Skill IDmicrosoft/amplifier-bundle-memory/skills/memory
Files2 files

Related skills

RememberSave what you typed as a memory, in your own words. `/remember <text>`.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.ChronicleAnalyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.Heap Snapshot AnalysisAnalyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.Memory Leak AuditAudit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.Playwright Test ResultsQuery Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.