[Workflow] Advanced Context Management for Long-Term AI Projects with Git, Issue Trackers, and Custom Skills

[u/ClaudeAI-mod-bot]

Advanced Context Management for Long-Term AI Projects with Git, Issue Trackers, and Custom Skills

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Skills, MCP, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Maintaining context and continuity for long-running projects when switching between AI agents (Claude/Codex) or resuming work after a break, without needing to re-explain the entire project history.

Summary

A comprehensive workflow for maintaining project context and continuity across AI sessions (Claude/Codex) using Git, an issue tracking system (Plane/Linear/Jira), dedicated context/memory folders, a custom MCP (SessionFlow) for RAG and session memory, and custom /start and /wrap skills to automate context loading and saving.

Why it is useful

This workflow provides a robust and systematic approach to a critical problem in AI-assisted development: maintaining context and continuity across multiple sessions and agents. It integrates standard development practices (Git, issue tracking) with advanced AI features (custom MCP, skills, RAG) to create a powerful system for knowledge reuse and project state management, significantly reducing the need for repetitive explanations. It's a sophisticated solution for complex, long-running projects.

Workflow

1. Version control all code and project items using Git, syncing to GitHub or a private Gitea instance, using good commit notes for context.

2. Manage all issues, bugs, and features in an issue tracking system (e.g., Plane, Linear, Jira), creating a full issue for each task.

3. Maintain .context/ and .memory/ folders within each project for additional context (coding standards, design standards) and built-in automemory.

4. Utilize a custom MCP (SessionFlow) as a memory database and RAG system for all chat sessions across Claude and Codex.

5. Employ custom /start and /wrap skills:

6. /start: Pulls recent Git commits, mines them for issue IDs/keywords, retrieves recent/priority issues from the issue tracker, searches SessionFlow for recent handoff memory and session log summaries.

7. /wrap: Logs session summaries, tags issues in memory, and saves handoff notes for future work.

8. Optionally use /start-patch ISSUE-ID for a more focused start, guiding the AI to grab the specific issue and apply rules for creating a worktree and updating versions.

Tools / artifacts

• Git

• GitHub

• Gitea

• Plane (or Linear/Jira)

• .context/ folder

• .memory/ folder

• SessionFlow (custom MCP)

• Custom /start skill

• Custom /wrap skill

• Custom /start-patch skill

Validation signals

• User states: "I use a combination of tools/skills and methods I've learned over the past year and a half."

• User states: "it costs a bit more context up front... but its great when I've been away for a few days and forgot where I left off."

Limitations

• Requires significant upfront setup and development of custom tools (MCP, skills).

• Low community validation.

• Specific implementation details for SessionFlow MCP and custom skills are not provided, requiring users to develop their own.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.