codemap_checklist_remove_item

Remove an item from a session checklist. Use codemap_checklist_list to see item IDs.

checklistworkflowsession

Parameters

NameTypeRequiredDescription
checklistIdstring✅ Required
itemIdstring✅ RequiredItem ID to remove

Usage Examples

MCP Usage (for AI Agents like Claude)

json
{
  "name": "codemap_checklist_remove_item",
  "arguments": {
    "itemId": "item-1712345678901"
  }
}

Example Output

JSON Response

json
{
  "success": true,
  "checklistId": "session:close-default",
  "itemId": "2",
  "message": "Removed item #2 from session:close-default"
}
ℹ️When to Use This Tool
    Use codemap_checklist_remove_item to clean up stale or irrelevant workflow checklist items. Remove items when:
  • Workflow changes - Process no longer relevant to current work ("Deploy to staging" when staging environment removed)
  • Tool changes - Replaced by better tools ("Run manual tests" when switching to automated CI/CD)
  • Automation - Task now automated elsewhere (pre-commit hooks handle linting, no need for manual reminder)
  • Redundancy - Covered by other checklist items ("Run tests" duplicated across multiple items)
  • Project phase - No longer applicable ("Sprint planning" reminder during maintenance phase)
  • Always list items first with codemap_checklist_list to find the correct itemId.
💡Common Patterns
Remove Outdated Items
// Step 1: List items to find IDs
{
"name": "codemap_checklist_list",
"arguments": {
"trigger": "session:close"
}
}

// Step 2: Remove outdated item
{
"name": "codemap_checklist_remove_item",
"arguments": {
"checklistId": "session:close-default",
"itemId": "2"
}
}


Clean Up Duplicates
// If multiple items say "Run tests", keep highest priority one and remove duplicates
{
"name": "codemap_checklist_remove_item",
"arguments": {
"checklistId": "session:close-default",
"itemId": "4"
}
}


Remove Automated Tasks
// If pre-commit hooks now handle linting, remove manual reminder
{
"name": "codemap_checklist_remove_item",
"arguments": {
"checklistId": "session:close-default",
"itemId": "3"
}
}
💡Pro Tips
Always list first - Item IDs shift when items are added/removed. What was ID "2" yesterday might be ID "1" today. Call codemap_checklist_list immediately before removing to confirm current IDs.

Replace, don't just remove - If removing an outdated item, consider adding an updated version with codemap_checklist_add_item. For example, if removing "Run manual tests", add "Verify CI/CD pipeline passed".

Team coordination - Checklists are version-controlled (.codemap/checklists.json). Discuss with team before removing items others might rely on. Consider lowering priority instead of removing entirely.

Keep essentials - Don't remove core workflow items like "Run npm test" or "Review NEXT_SESSION.md". These are critical quality gates.
Best Practices
  • List before removing - Always call codemap_checklist_list first to confirm the current item IDs. Item IDs can shift when items are added or removed.
  • Team communication - Discuss with team before removing shared checklist items. What seems irrelevant to you might be critical for others. Consider demoting priority from HIGH to MEDIUM instead of removing.
⚠️Common Mistakes
Mistake: Removing items without listing first, using old/guessed item IDs
Instead: Always run codemap_checklist_list({ trigger: 'session:close' }) first to see current item IDs, then immediately remove using the exact ID shown

Mistake: Removing items just because you personally don't use them
Instead: Since .codemap/checklists.json is version-controlled and shared, discuss with team before removing. The item might be critical for teammates. Consider lowering priority or making the text more specific instead of removing.