Full Development Lifecycle
Based on Damian Galarza's complete workflow documented in 'How I Use Claude Code.' This isn't about any single skill — it's about building a connected development environment. Claude accesses your project management (Linear/Jira), error tracking (Sentry), knowledge base (Obsidian), and persistent memory across sessions. Context is never lost between conversations.
MCP Servers
Sentry MCP
Production error tracking — triage and fix issues without leaving your agent.
Linear MCP
Issue tracking and project management — read tasks, update status, create issues.
GitHub MCP
Version control — commits, PRs, code review, and CI/CD status.
Memory MCP
Persistent memory across sessions — store implementation plans, decisions, and context.
Setup
Add the Sentry MCP server for production error tracking and triage.
{
"mcpServers": {
"sentry": { "url": "https://mcp.sentry.dev" }
}
}Add Linear or Jira MCP for issue tracking and status updates.
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@linear/mcp-server"],
"env": { "LINEAR_API_KEY": "<your-key>" }
}
}
}Add GitHub MCP for version control and PR management.
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "<your-token>" }
}
}
}Add the Memory MCP server so implementation plans persist across sessions.
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
}
}
}Point Claude at your Obsidian vault or notes directory for accumulated project context.
Use Cases
- End-to-end development workflow automation
- Cross-tool context sharing (PM + errors + code)
- Persistent memory across coding sessions
- Team lead workflows with multiple integrations