sync-notes

Synchronizes session context notes with a private GitHub repository across machines.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2 --skill sync-notes-palfish-t-i-u
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-notes
Source: https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2/tree/main/.claude/skills/sync-notes
Command: npx skills add https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2 --skill sync-notes-palfish-t-i-u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work sessions on the PalFish GMV project lose context when switching between machines, forcing you to re-explain decisions, task states, and technical findings. This Skill syncs structured notes to a private GitHub repo (palfish-internal-notes) so any machine can pick up exactly where another left off. ## Core Features & Use Cases - PULL mode: At session start, git-pulls the internal-notes repo, reads the README summary and relevant topic notes, then loads related code context from the GMV repo. - PUSH mode: At session end, writes a full-context note following a strict convention ({topic}-{YYYY-MM-DD}.md, project tag, code references like backend/activation_routes.py:1499), updates the README index, commits and pushes. - Safety rules: Never commits sensitive data (salaries, customer info, credentials), never force-pushes, and never deletes old notes. - Use Case: You finish debugging a SePay webhook issue on your office PC. Say "sync notes" and the findings, root cause, and follow-ups are pushed; the next morning your laptop pulls them and continues without re-investigation. ## Quick Start Say "sync notes" or "nối tiếp từ máy kia" to pull the latest context from the internal-notes repo, or ask to "cập nhật internal notes" to push the current session's findings.

Frequently Asked Questions about sync-notes

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

FAQPage Schema
How do I sync context notes between machines with git?

Use PULL mode at session start to git-pull the internal-notes repo and read the README summary plus relevant topic notes. Use PUSH mode at session end to write a dated Markdown note, update the README index, commit, and push.

What is the note file naming convention for cross-machine handoffs?

Notes are named {topic}-{YYYY-MM-DD}.md with a title line, a project tag line (Dự án: gmv), and full context body. Code references use relative paths from the repo root, such as backend/activation_routes.py:1499.

What happens if the internal-notes repo is not cloned locally?

The Skill clones it using the GitHub CLI: gh repo clone GiganticBakery/palfish-internal-notes into the local automation directory. After cloning, normal pull and push workflows apply.

What content is not allowed in synced notes?

Sensitive data is prohibited: raw salaries, HRIS dumps, customer information, and credentials. Empty or title-only notes are also rejected, and force push, interactive rebase, and deleting old notes are forbidden.

How are git conflicts avoided when pushing notes?

The Skill always runs git pull before writing or updating notes in PUSH mode. This fetches the latest state from other machines first, reducing the chance of merge conflicts on commit and push.