timothee
Community@t-mercier · Amsterdam
Software engineer @codam-coding-college | 42 Amsterdam.
Agent Skills by timothee
Showing 14 vetted skills indexed across 1 GitHub repositories.
t-mercierlearn
Writes durable user preferences, environment facts, and gotchas into a knowledge notes vault.
t-mercierroute
Builds a Context Brief from knowledge notes, past session notes, and ticket trackers before debugging.
t-mercierrestart-session
Wraps or resumes Claude Code sessions by loading notes.md context and syncing git branches.
t-mercierwrap-session
Summarizes a session conversation into notes.md and stamps the close marker headlessly.
t-mercierimport-session
Registers a running Claude Code session with a notes.md file under a configured category folder.
t-mercierclose-session
Summarizes the active session into its notes.md and appends a closing Session history entry.
t-merciersync-refs
Synchronizes session ticket statuses and pull request links from Jira and GitHub into notes frontmatter.
t-mercierskills-review
Review, approve, or reject staged skill proposals pending in the skills-pending directory.
t-mercierskills-curate
Audits a skill collection for stale entries and overlapping clusters, staging merge or archive proposals.
t-merciersave-session
Checkpoint an active session's decisions and progress into its registered notes.md without closing it.
t-mercierskill-propose
Capture reusable procedures from a session as new skills or patches to existing ones.
t-mercierrename-category
Renames a session category across config, folders, notes frontmatter, and active-sessions.json.
t-mercierstart-session
Creates a session notes folder, registers it in active-sessions.json, and rebases the git branch.
t-mercierarchive-session
Archives a stale session by stamping its notes.md and removing it from active-sessions.json.
Frequently Asked Questions About timothee
FAQPage SchemaWhat tasks can I accomplish with t-mercier's session skills?▼
You can start, save, close, restart, import, and archive Claude Code sessions, each tracked through a notes.md file and active-sessions.json registry. Additional skills sync ticket and pull-request frontmatter, rename categories across all references, and capture durable knowledge notes or reusable skill proposals.
Who are these skills designed for?▼
Software engineers using Claude Code who juggle multiple tickets, branches, and long-running sessions. They suit developers who want persistent session notes, context briefs before debugging, and a governed loop for turning corrections into reusable skills rather than re-explaining preferences every session.
How do the session skills work in practice?▼
Run /start-session with a category and ticket to create a notes folder and register the session. During work, /save-session checkpoints progress; /close-session summarizes decisions, files touched, and next steps. /restart-session <slug> later reloads that context and checks out the recorded branch.
What prerequisites and dependencies do these skills require?▼
They require a Claude Code environment with Bash, Read, Write, and Edit permissions, plus a configured categories setup defining note locations. Git integration applies only when the notes folder sits inside a repository, and /sync-refs additionally needs the gh CLI and a reachable ticket tracker.
How do the knowledge and skill-capture skills differ?▼
The /learn skill writes atomic notes about preferences, corrections, and environment facts into the knowledge vault. The /skill-propose skill captures reusable procedures as new or patched skills, applying them live with approval or staging them in ~/.claude/skills-pending/ for /skills-review.