workflow (truongfelix)
A Claude Code template: each session checks the last one's notes against git and GitHub, picks the day task and writes a handoff.
- 67 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The template runs shell scripts and, as configured in `/autonomy`, may commit, push and merge without asking.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add workflows/workflow-truongfelixDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The template runs shell scripts and, as configured in `/autonomy`, may commit, push and merge without asking.
This is third-party code. Review the repository files before installing.
What it does
The template tackles stale notes: a branch marked pushed that never reached the remote, a task still listed as running after it was closed. The `ground-truth.sh` script collects facts from git, GitHub and the machine, and notes from the last session count only as a claim checked against those facts. `/session-start` shows the mismatches and proposes the day's task, `/handoff` records the state for the next session, `/board` gathers backlog and decisions on one page. `/autonomy` and `/checks` set what Claude does without asking and how code is checked before a merge. The template is copied into a project by `bin/adopt.sh`.
Who it is for. Developers running a long project in Claude Code across sessions with gaps who lose context between them.
Good fit when
- On Monday work started on Friday continues without trusting an outdated note.
- Several sessions work on a project and claim different parts of the backlog.
- A developer wants a list of actions Claude may take unasked: commit, push, merge.
- Owner decisions need to accumulate and not be reopened by a new session.
Not a fit when
- The project has no git repository or remote.
- A ready team system in a task tracker is required, with no files in a repository.
- The task is one-off and notes between sessions are not needed.
Example request
Run `/session-start`, show where yesterday's handoff disagrees with git and propose one task for today.Limitations
bash and git with a remote are needed; the GitHub CLI `gh` is optional for PRs and CI, and systemd for background jobs. It runs on Linux, macOS and Windows under Git Bash or WSL. The template installs by copying and sessions write their edits into its files. A single author maintains it, and the last commit is dated 14 October 2026. The template rules fit one developer or a small team; a large team would need to revisit them.
How to disable. Delete the template `.claude/` skills directory plus `BACKLOG.md`, `questions.md`, `notes/` and the section in `CLAUDE.md` once they are not needed. Git keeps the history, so they can be restored.
FAQ
How does a handoff differ from ordinary notes?
A handoff counts as a claim, and `ground-truth.sh` provides facts from git, GitHub and the machine. The session compares them first and reports where they disagree.
What is stored in project files?
Session handoffs in `notes/handoff/`, the backlog in `BACKLOG.md`, decisions in `questions.md`, lessons in `notes/lessons.md` and rules in `CLAUDE.md`.
Can notes live in a separate repository?
Yes. Notes sit with the code or in a private repo, and `attach.sh` attaches another code repository later.
How is the template upgraded?
Update the clone with `git pull` and ask Claude to follow `UPGRADE.md`; earlier versions upgrade through the same steps.
Is the GitHub CLI required?
No, `gh` is optional. With it the template sees open pull requests and CI, without it the check runs on git and local notes.
Discussion
No questions or reviews yet.
Related
WorkflowsA skill that keeps discussion and decisions in GitHub issues and PRs so the next agent session picks up where you stopped.
A Claude Code plugin that replaces auto-compact: it writes a handoff brief, clears the session and continues from it
A skill that keeps project memory in plain Markdown files: session logs, a wiki, rules, a to-do list and a note on where to resume
Claude Code Toolkit (robertguss)
Claude Code Toolkit
A set of Claude Code skills and hooks: brainstorming, worker-led project leadership, a wiki, and a book pipeline.
A Claude Desktop template where nine scheduled tasks build a morning brief from email, WhatsApp and calendar.
claude-history searches and opens past Claude Code, Codex and Pi conversations in the terminal and gives Claude a history skill
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| workflow (truongfelix) (this card) | no | 67 | |
| auto-handoff | no | 106 | preserves context across sessions; workflow checks notes against git and GitHub and adds a backlog, decisions and autonomy settings |
| claude-auto-handoff | no | 125 | automates the handoff itself; workflow builds fact checking and a daily task around it |
README in short
The README's main argument is that notes on work state go stale, so a script checks them against git before every session. PRINCIPLES.md explains which failure each rule grew from.