skills.rest
QuyDu
QuyDuCOMMUNITY
Explore all skills by this author →
GitHub

project-memory

Maintains durable project preferences and memory entries scoped across user, session, and repository contexts.

Updated Aug 1, 2026
Search Tags:#memory management#governance#preferences#session state#knowledge retention#github copilot#precedence rules
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-memory-quydu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-memory
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/project-memory
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-memory-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose hard-won operational knowledge between sessions, and stale notes can silently contradict current repository state. This Skill records durable working preferences while enforcing that current instructions and repository evidence always outrank saved memory. ## Core Features & Use Cases - Scoped Memory Management: Stores concise entries across user, session, and repository scopes with correct retention boundaries. - Precedence Enforcement: Applies rules so current user instructions and verified repository evidence override any stored memory. - Stale Memory Cleanup: Removes or downgrades entries that conflict with authoritative evidence, with an auditable update report. - Use Case: After several sessions confirm a repository convention, record it in repository-scoped memory; later, when the convention changes, retire the outdated note and publish a report of additions, revisions, and removals. ## Quick Start Ask the agent to record the verified branching convention into repository-scoped memory and produce the project-memory update report.

Frequently Asked Questions about project-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist project preferences across AI sessions?▼

Record verified preferences as concise memory entries scoped to user, session, or repository level. Each entry must reference authoritative supporting evidence, and an update report documents every addition, revision, and removal.

What happens when stored memory conflicts with current instructions?▼

Current user instructions and repository evidence always override stored memory. When a precedence conflict cannot be resolved, the previous memory state is preserved and the uncertain update is not persisted.

Can project memory override repository evidence?▼

No. The skill explicitly forbids using stored memory to override the current request or repository evidence. Entries that contradict verified repository state are removed or downgraded.

What outputs does the project-memory skill produce?▼

It writes two owned reports: reports/project-memory.json and reports/project-memory.md. These summarize memory additions, revisions, removals, and the rationale behind each change.

When does the skill refuse to save a memory entry?▼

It fails closed when evidence does not support the proposed update, and never persists uncertain claims as durable memory. Deleting broad memory scopes or exporting memory externally requires explicit approval.

Related Skills

Explore More Software Engineering Skills→
changfengprochangfengpro

self-improving-agent

Captures skill experiences into multi-memory artifacts and proposes validated skill updates.

Community
Advanced
maruakshaymaruakshay
4

memory-security

Audit memory write, retrieval, and retention paths to prevent cross-session leakage.

Community
Advanced
bhaumikmaanbhaumikmaan
3

knowledge-management

Classify, store, and retrieve project knowledge across sessions using structured memory frontmatter.

Community
Advanced
vrcmsvrcms
1

knowledge-ops

Synchronize knowledge across local files, MCP memory, and external repositories.

Community
Advanced