resolve
doc-sentinel:resolve
Process accumulated drift warnings from .doc-sentinel-drift.json. For each warning, verify whether the doc actually drifted, fix it if so, or dismiss if it is a false positive.
Phase 1: Load Drift Queue
cat .doc-sentinel-drift.json 2>/dev/null || echo "No drift warnings pending"
If the file is empty or missing, report "No drift warnings to resolve" and exit.
Phase 2: Deduplicate and Group
Group warnings by doc file. Multiple source changes may affect the same doc — process them together for coherent updates.
Example grouping:
More from dgalarza/claude-code-workflows
process-meeting-transcript
Process raw meeting transcripts from Granola or other sources into structured notes with frontmatter, action items, summary, and formatted transcript. Use this skill when the user asks to process a meeting transcript or provides a raw transcript that needs formatting.
43tdd-workflow
Use this skill whenever you are implementing a feature using TDD.
38conventional-commits
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
32linear-implement
This skill should be used when implementing features from Linear issues with full TDD workflow, automated planning, parallel code reviews (security and Rails best practices), systematic feedback implementation, and automated PR creation with Linear integration. Use when the user provides a Linear issue ID (e.g., "TRA-9", "DEV-123") and wants a complete implementation workflow from issue to PR.
29rspec-testing
This skill should be used when writing, reviewing, or improving RSpec tests for Ruby on Rails applications. Use this skill for all testing tasks including model specs, controller specs, system specs, component specs, service specs, and integration tests. The skill provides comprehensive RSpec best practices from Better Specs and thoughtbot guides.
20parallel-code-review
This skill should be used when performing comprehensive code reviews using multiple specialized review agents in parallel. It provides patterns for concurrent execution, decision tracking to prevent redundancy, and consolidated reporting. Use when needing thorough review coverage from multiple perspectives (security, architecture, performance) or when reviewing large changesets.
20