skills.rest
Kevin-Mok
Kevin-MokCOMMUNITY
Explore all skills by this author →
Website𝕏@Kev_MokGitHub

feedback-memory

Read and append durable user feedback to a repo-tracked feedback.log.

Updated Aug 23, 2026
Search Tags:#workflow#feedback#memory#session-management#preferences#log#append-only
One-click install
npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill feedback-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-memory
Source: https://github.com/Kevin-Mok/ai-cli-dotfiles/tree/main/dot_agents/skills/feedback-memory
Command: npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill feedback-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist durable user corrections and preferences across sessions by maintaining a repo-tracked plain-text log named feedback.log, ensuring guidance about workflow, formatting, tooling, or communication can carry over between sessions.

Core Features & Use Cases

  • Read and apply canonical feedback at session start to influence behavior.
  • Append new durable feedback to the canonical log without rewriting existing entries.
  • Respect a defined log path and avoid logging ephemeral or task-specific data.

Quick Start

Read the canonical feedback.log at startup and apply any durable guidance before proceeding.

Frequently Asked Questions about feedback-memory

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

FAQPage Schema
How do I persist user corrections and preferences across sessions?▼

To persist user corrections across sessions, maintain a repo-tracked plain-text feedback.log that applies durable guidance at session start and appends new entries without rewriting existing logs.

What is the best way to carry over workflow and formatting feedback between coding sessions?▼

Carrying over workflow feedback between sessions requires a canonical log file that stores durable guidance in plain text, ensuring instructions regarding tooling and communication persist independently of session memory.

How do I apply durable feedback at session start without losing previous logs?▼

Applying durable feedback at session start involves reading the canonical log from a defined path and appending new entries, deliberately avoiding rewriting existing entries to preserve the full historical guidance.

Can I use an append-only log to manage session preferences for a specific repository?▼

Yes, you can use an append-only log to manage session preferences by tracking a feedback.log file within your repository, which ensures durable corrections are version-controlled and applied consistently.

When should I not use a feedback log for session management?▼

You should not use a feedback log for session management when dealing with ephemeral or task-specific data, as the log is designed exclusively for durable user corrections and long-term workflow preferences.

Related Skills

Explore More Software Engineering Skills→
rethinkhealthrethinkhealth
6

todo-create

Persist durable work items as markdown todos in a canonical path.

Official
Intermediate
danmestasdanmestas
4

takeoff

Inventory repository state and recent context to orient agent sessions.

Community
Intermediate
schneidermuschneidermu

ml-researcher-profile

Synchronize researcher identity and tool preferences across Cursor, Codex, and Claude Code.

Community
Advanced
maverick-mamamaverick-mama
6

companion-memory-persistence

Load identity and continuity data across NESTeq, file-based, and database-backed memory systems.

Community
Advanced