chore: fix CI checker, improve it#1099
Merged
Crunchyman-ralph merged 3 commits intonextfrom Aug 7, 2025
Merged
Conversation
|
Contributor
WalkthroughThis update revises pre-release configuration and workflow logic, updates changelogs and package versions, and documents new features. The Changes
Sequence Diagram(s)sequenceDiagram
participant Workflow as Pre-release Workflow
participant Config as .changeset/pre.json
Workflow->>Config: Check if .changeset/pre.json exists
alt File exists
Workflow->>Config: Read mode and tag
alt mode == "exit"
Workflow->>Workflow: Enter RC mode
else mode == "pre" and tag != "rc"
Workflow->>Workflow: Exit pre mode, enter RC mode
else mode == "pre" and tag == "rc"
Workflow->>Workflow: Already in RC mode
else Unknown mode
Workflow->>Workflow: Enter RC mode
end
else File does not exist
Workflow->>Workflow: Enter RC mode
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (4)
🧰 Additional context used📓 Path-based instructions (1)package.json📄 CodeRabbit Inference Engine (.cursor/rules/test_workflow.mdc)
Files:
🧠 Learnings (38)📓 Common learnings📚 Learning: document breaking changes...Applied to files:
📚 Learning: guidelines for using changesets (npm run changeset) to manage versioning and changelogs (changeset.m...Applied to files:
📚 Learning: applies to package.json : add and update test scripts in package.json to include test, test:watch, t...Applied to files:
📚 Learning: in monorepos, local packages should use "*" as the version constraint in package.json dependencies, ...Applied to files:
📚 Learning: for cli usage, install taskmaster globally with `npm install -g task-master-ai` or use locally via `...Applied to files:
📚 Learning: use the global `task-master` cli command instead of directly invoking `node scripts/dev.js` for all ...Applied to files:
📚 Learning: start new projects by running `task-master init` or `node scripts/dev.js parse-prd --input=
package.jsonapps/extension/package.jsonapps/extension/package.publish.jsonapps/extension/package.mjs📚 Learning: use `task-master add-task` to add a new task to tasks.json using ai....Applied to files:
📚 Learning: applies to scripts/modules/task-manager.js : the default tag 'master' must be used for all existing ...Applied to files:
📚 Learning: in the eyaltoledano/claude-task-master repository, the mcp server code in mcp-server/src/ is part of...Applied to files:
📚 Learning: in the eyaltoledano/claude-task-master repository, the vs code extension uses a 3-file packaging sys...Applied to files:
📚 Learning: applies to .taskmaster/config.json : store taskmaster configuration settings (ai model selections, p...Applied to files:
📚 Learning: applies to scripts/modules/task-manager.js : extract tasks from prd documents using ai, create them ...Applied to files:
📚 Learning: generate task files with `task-master generate` after updating tasks.json....Applied to files:
📚 Learning: use `task-master fix-dependencies` to find and fix all invalid dependencies in tasks.json and task f...Applied to files:
📚 Learning: applies to scripts/modules/task-manager.js : use consistent formatting for task files, include all t...Applied to files:
📚 Learning: applies to .taskmaster/config.json : do not manually edit `.taskmaster/config.json` unless you are c...Applied to files:
📚 Learning: use `task-master validate-dependencies` to check for and identify invalid dependencies in tasks.json...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/**/*.js : do not call ai-specific getters (like `getmainmode...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/*.js : do not initialize ai clients (anthropic, perplexity, ...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/*.js : do not implement fallback or retry logic outside `ai-...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/*.js : do not import or call anything from the old `ai-servi...Applied to files:
📚 Learning: when implementation differs significantly from planned approach, call `node scripts/dev.js update --...Applied to files:
📚 Learning: applies to scripts/modules/task-manager/*.js : do not fetch ai-specific parameters (model id, max to...Applied to files:
📚 Learning: applies to tasks.json : use the `tasks.json` file (generated by taskmaster) to store the project's t...Applied to files:
📚 Learning: applies to scripts/modules/task-manager.js : tasks must be organized into separate contexts (tags) w...Applied to files:
📚 Learning: applies to .taskmaster/config.json : all other taskmaster settings (model choice, max tokens, temper...Applied to files:
📚 Learning: applies to .taskmaster/config.json : do not manually edit the .taskmaster/config.json file; always u...Applied to files:
📚 Learning: applies to .taskmaster/config.json : do not manually edit the .taskmaster/config.json file. use the ...Applied to files:
📚 Learning: applies to scripts/modules/commands.js : implement semantic version comparison and display attractiv...Applied to files:
📚 Learning: applies to scripts/modules/commands.js : implement version checking to notify users of available upd...Applied to files:
📚 Learning: applies to scripts/modules/*.js : ensure new features work with existing projects seamlessly, suppor...Applied to files:
📚 Learning: applies to scripts/modules/dependency-manager.js : track and report changes made during dependency c...Applied to files:
📚 Learning: applies to scripts/modules/commands.js : integrate version checking in the cli run function, startin...Applied to files:
📚 Learning: applies to scripts/modules/dependency-manager.js : format task and dependency ids consistently when ...Applied to files:
📚 Learning: applies to scripts/modules/dependency-manager.js : remove references to non-existent tasks during va...Applied to files:
📚 Learning: applies to scripts/modules/dependency-manager.js : convert between formats appropriately when needed...Applied to files:
🔇 Additional comments (6)
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Crunchyman-ralph
temporarily deployed
to
extension-release
GitHub Actions
Inactive
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
🔭 Outside diff range comments (1)
package.json (1)
16-24: Missingtest:*scripts required by team conventionsPer the repository’s coding guidelines,
package.jsonshould expose the full test matrix (test,test:watch,test:coverage,test:unit,test:integration,test:e2e,test:ci).
Only some of these are present. Consider stubbing the missing ones so CI jobs don’t fail when they call them."scripts": { "test": "node --experimental-vm-modules node_modules/.bin/jest", + "test:unit": "npm run test -- --runTestsByPath tests/unit", + "test:integration": "npm run test -- --runTestsByPath tests/integration", "test:fails": "node --experimental-vm-modules node_modules/.bin/jest --onlyFailures", "test:watch": "node --experimental-vm-modules node_modules/.bin/jest --watch", "test:coverage": "node --experimental-vm-modules node_modules/.bin/jest --coverage", + "test:ci": "npm run test -- --ci",
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (6)
.changeset/pre.json(1 hunks).github/workflows/pre-release.yml(1 hunks)CHANGELOG.md(1 hunks)apps/extension/CHANGELOG.md(1 hunks)apps/extension/package.json(4 hunks)package.json(2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
.changeset/*
📄 CodeRabbit Inference Engine (.cursor/rules/new_features.mdc)
Create appropriate changesets for new features, use semantic versioning, include tagged system information in release notes, and document breaking changes if any.
Files:
.changeset/pre.json
package.json
📄 CodeRabbit Inference Engine (.cursor/rules/test_workflow.mdc)
Add and update test scripts in package.json to include test, test:watch, test:coverage, test:unit, test:integration, test:e2e, and test:ci
Files:
package.json
🧠 Learnings (58)
📓 Common learnings
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.810Z
Learning: Pull Request descriptions must use the provided template, including Task Overview, Subtasks Completed, Implementation Details, Testing, Breaking Changes, and Related Tasks
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1069
File: .changeset/fix-tag-complexity-detection.md:0-0
Timestamp: 2025-08-02T15:33:22.656Z
Learning: For changeset files (.changeset/*.md), Crunchyman-ralph prefers to ignore formatting nitpicks about blank lines between frontmatter and descriptions, as he doesn't mind having them and wants to avoid such comments in future reviews.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Every pull request containing new features, bug fixes, breaking changes, performance improvements, significant refactoring, user-facing documentation updates, dependency updates, or impactful build/tooling changes should include a changeset file.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/git_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:31.810Z
Learning: Pull Request titles must follow the format: Task <ID>: <Task Title>
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Do not add a changeset for trivial chores such as very minor code cleanup, adding comments that don't clarify behavior, or typo fixes in non-user-facing code or internal docs.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/new_features.mdc:0-0
Timestamp: 2025-07-18T17:12:57.903Z
Learning: Applies to .changeset/* : Create appropriate changesets for new features, use semantic versioning, include tagged system information in release notes, and document breaking changes if any.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs (changeset.mdc).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : The changeset summary should be user-facing, describing what changed in the released version that is relevant to users or consumers of the package.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : When running `npm run changeset` or `npx changeset add`, provide a concise summary of the changes for the `CHANGELOG.md` in imperative mood, typically a single line, and not a detailed Git commit message.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Always stage and commit the generated `.changeset/*.md` file along with your relevant code changes.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/self_improve.mdc:0-0
Timestamp: 2025-07-18T17:13:11.229Z
Learning: Document breaking changes
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#992
File: .coderabbit.yaml:1-169
Timestamp: 2025-07-16T16:06:07.169Z
Learning: CodeRabbit configuration files like .coderabbit.yaml are internal development tooling that affect the review process but don't impact end users, so changesets are not required for these configuration additions.
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Do not add a changeset for local configuration changes, such as updates to personal editor settings or local `.env` files.
📚 Learning: in the eyaltoledano/claude-task-master repository, the mcp server code in mcp-server/src/ is part of...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1002
File: .changeset/puny-friends-give.md:2-3
Timestamp: 2025-07-17T21:33:57.585Z
Learning: In the eyaltoledano/claude-task-master repository, the MCP server code in mcp-server/src/ is part of the main "task-master-ai" package, not a separate "mcp-server" package. When creating changesets for MCP server changes, use "task-master-ai" as the package name.
Applied to files:
apps/extension/CHANGELOG.mdpackage.jsonCHANGELOG.md
📚 Learning: applies to .changeset/*.md : the changeset summary should be user-facing, describing what changed in...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : The changeset summary should be user-facing, describing what changed in the released version that is relevant to users or consumers of the package.
Applied to files:
apps/extension/CHANGELOG.md.changeset/pre.json.github/workflows/pre-release.yml
📚 Learning: document breaking changes...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/self_improve.mdc:0-0
Timestamp: 2025-07-18T17:13:11.229Z
Learning: Document breaking changes
Applied to files:
apps/extension/CHANGELOG.mdpackage.json
📚 Learning: applies to .changeset/*.md : when running `npm run changeset` or `npx changeset add`, provide a conc...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Applies to .changeset/*.md : When running `npm run changeset` or `npx changeset add`, provide a concise summary of the changes for the `CHANGELOG.md` in imperative mood, typically a single line, and not a detailed Git commit message.
Applied to files:
apps/extension/CHANGELOG.md.changeset/pre.jsonCHANGELOG.md
📚 Learning: guidelines for using changesets (npm run changeset) to manage versioning and changelogs (changeset.m...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs (changeset.mdc).
Applied to files:
apps/extension/CHANGELOG.md.changeset/pre.json.github/workflows/pre-release.ymlpackage.json
📚 Learning: in the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#997
File: apps/extension/src/services/task-repository.ts:25-57
Timestamp: 2025-07-31T21:48:00.389Z
Learning: In the eyaltoledano/claude-task-master repository, every task is always part of a tag - there is no concept of untagged tasks. The tag system is mandatory and comprehensive, meaning all tasks exist within a tag context (with 'master' as the default tag if none specified).
Applied to files:
apps/extension/CHANGELOG.mdCHANGELOG.md
📚 Learning: use the taskmaster command set (`task-master` cli or mcp tools) for all task management operations: ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: Use the Taskmaster command set (`task-master` CLI or MCP tools) for all task management operations: listing, expanding, updating, tagging, and status changes.
Applied to files:
apps/extension/CHANGELOG.mdCHANGELOG.md
📚 Learning: import task master's development workflow commands and guidelines, treat as if import is in the main...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-31T22:07:14.034Z
Learning: Import Task Master's development workflow commands and guidelines, treat as if import is in the main CLAUDE.md file.
Applied to files:
apps/extension/CHANGELOG.mdCHANGELOG.md
📚 Learning: guidelines for integrating new features into the task master cli with tagged system considerations (...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for integrating new features into the Task Master CLI with tagged system considerations (new_features.mdc).
Applied to files:
apps/extension/CHANGELOG.mdapps/extension/package.json.changeset/pre.jsonCHANGELOG.md
📚 Learning: comprehensive reference for taskmaster mcp tools and cli commands with tagged task lists information...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Comprehensive reference for Taskmaster MCP tools and CLI commands with tagged task lists information (taskmaster.mdc).
Applied to files:
apps/extension/CHANGELOG.mdCHANGELOG.md
📚 Learning: in monorepos, local packages should use "*" as the version constraint in package.json dependencies, ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1090
File: apps/extension/package.json:241-243
Timestamp: 2025-08-07T13:00:22.923Z
Learning: In monorepos, local packages should use "*" as the version constraint in package.json dependencies, as recommended by npm. This ensures the local version from within the same workspace is always used, rather than attempting to resolve from external registries. This applies to packages like task-master-ai within the eyaltoledano/claude-task-master monorepo.
Applied to files:
apps/extension/CHANGELOG.mdapps/extension/package.jsonpackage.json
📚 Learning: for cli usage, install taskmaster globally with `npm install -g task-master-ai` or use locally via `...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: For CLI usage, install Taskmaster globally with `npm install -g task-master-ai` or use locally via `npx task-master-ai ...`.
Applied to files:
apps/extension/CHANGELOG.mdapps/extension/package.jsonpackage.jsonCHANGELOG.md
📚 Learning: describes the high-level architecture of the task master cli application, including the new tagged t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Describes the high-level architecture of the Task Master CLI application, including the new tagged task lists system (architecture.mdc).
Applied to files:
apps/extension/CHANGELOG.mdCHANGELOG.md
📚 Learning: maintain valid dependency structure with `task-master fix-dependencies` when needed....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Maintain valid dependency structure with `task-master fix-dependencies` when needed.
Applied to files:
apps/extension/CHANGELOG.md
📚 Learning: in the eyaltoledano/claude-task-master repository, the vs code extension uses a 3-file packaging sys...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#997
File: apps/extension/package.publish.json:2-8
Timestamp: 2025-07-31T20:49:04.638Z
Learning: In the eyaltoledano/claude-task-master repository, the VS Code extension uses a 3-file packaging system where package.json (with name "extension") is for development within the monorepo, while package.publish.json (with name "task-master-hamster") contains the clean manifest for VS Code marketplace publishing. The different names are intentional and serve distinct purposes in the build and publishing workflow.
Applied to files:
apps/extension/package.jsonpackage.json
📚 Learning: applies to scripts/modules/task-manager.js : use consistent formatting for task files, include all t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Use consistent formatting for task files, include all task properties in text files, and format dependencies with status indicators.
Applied to files:
apps/extension/package.json.changeset/pre.json
📚 Learning: applies to .taskmaster/config.json : do not manually edit `.taskmaster/config.json` unless you are c...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: Applies to .taskmaster/config.json : Do not manually edit `.taskmaster/config.json` unless you are certain of the changes; use the `task-master models` command or `models` MCP tool for configuration.
Applied to files:
apps/extension/package.json
📚 Learning: applies to .taskmaster/config.json : store taskmaster configuration settings (ai model selections, p...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:02.683Z
Learning: Applies to .taskmaster/config.json : Store Taskmaster configuration settings (AI model selections, parameters, logging level, default subtasks/priority, project name, tag management) in `.taskmaster/config.json` in the project root. Do not configure these via environment variables.
Applied to files:
apps/extension/package.jsonpackage.json
📚 Learning: generate task files with `task-master generate` after updating tasks.json....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Generate task files with `task-master generate` after updating tasks.json.
Applied to files:
apps/extension/package.json
📚 Learning: applies to .taskmaster/config.json : do not manually edit the .taskmaster/config.json file; always u...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: Applies to .taskmaster/config.json : Do not manually edit the .taskmaster/config.json file; always use the provided CLI or MCP tools for configuration changes.
Applied to files:
apps/extension/package.json
📚 Learning: applies to .taskmaster/config.json : do not manually edit the .taskmaster/config.json file. use the ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: Applies to .taskmaster/config.json : Do not manually edit the .taskmaster/config.json file. Use the included commands either in the MCP or CLI format as needed. Always prioritize MCP tools when available and use the CLI as a fallback.
Applied to files:
apps/extension/package.json
📚 Learning: applies to scripts/modules/task-manager.js : tasks must be organized into separate contexts (tags) w...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Tasks must be organized into separate contexts (tags) within tasks.json, using the tagged format: {"master": {"tasks": [...]}, "feature-branch": {"tasks": [...]}}. Legacy format {"tasks": [...]} must be silently migrated to the tagged format on first use.
Applied to files:
apps/extension/package.json.changeset/pre.json
📚 Learning: applies to .taskmaster/config.json : all other taskmaster settings (model choice, max tokens, temper...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: Applies to .taskmaster/config.json : All other Taskmaster settings (model choice, max tokens, temperature, log level, custom endpoints) are managed in .taskmaster/config.json via the task-master models command or models MCP tool.
Applied to files:
apps/extension/package.json
📚 Learning: applies to tasks.json : use the `tasks.json` file (generated by taskmaster) to store the project's t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: Applies to tasks.json : Use the `tasks.json` file (generated by Taskmaster) to store the project's task list, including tags and task structures.
Applied to files:
apps/extension/package.json
📚 Learning: applies to scripts/modules/task-manager.js : the default tag 'master' must be used for all existing ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : The default tag 'master' must be used for all existing and new tasks unless otherwise specified.
Applied to files:
apps/extension/package.json.changeset/pre.jsonpackage.json
📚 Learning: applies to scripts/modules/task-manager.js : each task object must include all required properties (...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Each task object must include all required properties (id, title, description, status, dependencies, priority, details, testStrategy, subtasks) and provide default values for optional properties. Extra properties not in the standard schema must not be added.
Applied to files:
apps/extension/package.json
📚 Learning: use `task-master validate-dependencies` to check for and identify invalid dependencies in tasks.json...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use `task-master validate-dependencies` to check for and identify invalid dependencies in tasks.json and task files.
Applied to files:
apps/extension/package.json
📚 Learning: use `task-master fix-dependencies` to find and fix all invalid dependencies in tasks.json and task f...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use `task-master fix-dependencies` to find and fix all invalid dependencies in tasks.json and task files.
Applied to files:
apps/extension/package.json
📚 Learning: use `task-master add-task` to add a new task to tasks.json using ai....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use `task-master add-task` to add a new task to tasks.json using AI.
Applied to files:
apps/extension/package.jsonpackage.json
📚 Learning: start new projects by running `task-master init` or `node scripts/dev.js parse-prd --input=
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Start new projects by running `task-master init` or `node scripts/dev.js parse-prd --input=<prd-file.txt>` to generate the initial tasks.json.
Applied to files:
apps/extension/package.jsonpackage.json
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Start new projects by running `task-master init` or `node scripts/dev.js parse-prd --input=<prd-file.txt>` to generate the initial tasks.json.
apps/extension/package.jsonpackage.json📚 Learning: use the global `task-master` cli command instead of directly invoking `node scripts/dev.js` for all ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: Use the global `task-master` CLI command instead of directly invoking `node scripts/dev.js` for all task management operations.
Applied to files:
apps/extension/package.jsonpackage.json
📚 Learning: applies to .changeset/* : create appropriate changesets for new features, use semantic versioning, i...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/new_features.mdc:0-0
Timestamp: 2025-07-18T17:12:57.903Z
Learning: Applies to .changeset/* : Create appropriate changesets for new features, use semantic versioning, include tagged system information in release notes, and document breaking changes if any.
Applied to files:
.changeset/pre.json.github/workflows/pre-release.yml
📚 Learning: always stage and commit the generated `.changeset/*.md` file along with your relevant code changes....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Always stage and commit the generated `.changeset/*.md` file along with your relevant code changes.
Applied to files:
.changeset/pre.json.github/workflows/pre-release.yml
📚 Learning: do not add a changeset for local configuration changes, such as updates to personal editor settings ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Do not add a changeset for local configuration changes, such as updates to personal editor settings or local `.env` files.
Applied to files:
.changeset/pre.json
📚 Learning: for changeset files (.changeset/*.md), avoid suggesting punctuation for bullet points as the project...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1035
File: .changeset/quiet-rabbits-bathe.md:5-10
Timestamp: 2025-07-23T16:03:42.784Z
Learning: For changeset files (.changeset/*.md), avoid suggesting punctuation for bullet points as the project intentionally omits punctuation to make the generated changelog feel more natural.
Applied to files:
.changeset/pre.json
📚 Learning: every pull request containing new features, bug fixes, breaking changes, performance improvements, s...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/changeset.mdc:0-0
Timestamp: 2025-07-18T17:07:53.100Z
Learning: Every pull request containing new features, bug fixes, breaking changes, performance improvements, significant refactoring, user-facing documentation updates, dependency updates, or impactful build/tooling changes should include a changeset file.
Applied to files:
.changeset/pre.json
📚 Learning: for changeset files (.changeset/*.md), the first line after the frontmatter must be a plain, unstyle...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1091
File: .changeset/wide-actors-report.md:0-0
Timestamp: 2025-08-06T21:14:23.011Z
Learning: For changeset files (.changeset/*.md), the first line after the frontmatter must be a plain, unstyled summary line that gets integrated directly into the changelog. Do not add markdown headings or styling as this would interfere with the changelog generation process. Ignore markdownlint MD041 rule for these files.
Applied to files:
.changeset/pre.json
📚 Learning: for changeset files (.changeset/*.md), crunchyman-ralph prefers to ignore formatting nitpicks about ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1069
File: .changeset/fix-tag-complexity-detection.md:0-0
Timestamp: 2025-08-02T15:33:22.656Z
Learning: For changeset files (.changeset/*.md), Crunchyman-ralph prefers to ignore formatting nitpicks about blank lines between frontmatter and descriptions, as he doesn't mind having them and wants to avoid such comments in future reviews.
Applied to files:
.changeset/pre.json
📚 Learning: when implementation differs significantly from planned approach, call `node scripts/dev.js update --...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/.windsurfrules:0-0
Timestamp: 2025-07-18T17:19:27.365Z
Learning: When implementation differs significantly from planned approach, call `node scripts/dev.js update --from=<futureTaskId> --prompt="<explanation>"` to update tasks.json.
Applied to files:
.changeset/pre.jsonpackage.json
📚 Learning: applies to scripts/modules/task-manager.js : extract tasks from prd documents using ai, create them ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tasks.mdc:0-0
Timestamp: 2025-07-18T17:14:29.399Z
Learning: Applies to scripts/modules/task-manager.js : Extract tasks from PRD documents using AI, create them in the current tag context (defaulting to 'master'), provide clear prompts to guide AI task generation, and validate/clean up AI-generated tasks.
Applied to files:
.changeset/pre.jsonpackage.json
📚 Learning: applies to .taskmaster/state.json : track taskmaster's current tag context and migration status in `...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:12.881Z
Learning: Applies to .taskmaster/state.json : Track Taskmaster's current tag context and migration status in `.taskmaster/state.json`, which is automatically created and managed by the system.
Applied to files:
.changeset/pre.json
📚 Learning: applies to scripts/modules/dependency-manager.js : remove references to non-existent tasks during va...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dependencies.mdc:0-0
Timestamp: 2025-07-18T17:09:45.690Z
Learning: Applies to scripts/modules/dependency-manager.js : Remove references to non-existent tasks during validation
Applied to files:
.changeset/pre.json
📚 Learning: applies to scripts/modules/* : every command that reads or writes tasks.json must be tag-aware...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tags.mdc:0-0
Timestamp: 2025-07-18T17:13:30.188Z
Learning: Applies to scripts/modules/* : Every command that reads or writes tasks.json must be tag-aware
Applied to files:
.changeset/pre.json
📚 Learning: applies to package.json : add and update test scripts in package.json to include test, test:watch, t...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/test_workflow.mdc:0-0
Timestamp: 2025-08-03T12:13:33.875Z
Learning: Applies to package.json : Add and update test scripts in package.json to include test, test:watch, test:coverage, test:unit, test:integration, test:e2e, and test:ci
Applied to files:
package.json
📚 Learning: applies to scripts/modules/**/*.test.js : test cli and mcp interfaces with real task data, verify en...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/new_features.mdc:0-0
Timestamp: 2025-07-18T17:12:57.903Z
Learning: Applies to scripts/modules/**/*.test.js : Test CLI and MCP interfaces with real task data, verify end-to-end workflows across tag contexts, and test error scenarios and recovery in integration tests.
Applied to files:
package.json
📚 Learning: applies to **/*.test.js : do not modify real task files (tasks.json) during tests....
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tests.mdc:0-0
Timestamp: 2025-07-18T17:16:13.793Z
Learning: Applies to **/*.test.js : Do not modify real task files (tasks.json) during tests.
Applied to files:
package.json
📚 Learning: applies to mcp-server/src/{core/utils,tools}/**/*.js : place utilities specifically designed to supp...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/utilities.mdc:0-0
Timestamp: 2025-07-18T17:18:17.759Z
Learning: Applies to mcp-server/src/{core/utils,tools}/**/*.js : Place utilities specifically designed to support the MCP server implementation into the appropriate subdirectories within `mcp-server/src/` (e.g., path/core logic helpers in `mcp-server/src/core/utils/`, tool execution/response helpers in `mcp-server/src/tools/utils.js`).
Applied to files:
package.json
📚 Learning: applies to **/*.test.js : use test-specific file paths (e.g., 'test-tasks.json') for all file operat...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/tests.mdc:0-0
Timestamp: 2025-07-18T17:16:13.793Z
Learning: Applies to **/*.test.js : Use test-specific file paths (e.g., 'test-tasks.json') for all file operations in tests.
Applied to files:
package.json
📚 Learning: applies to scripts/modules/*.js : each module in scripts/modules/ should be focused on a single resp...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/architecture.mdc:0-0
Timestamp: 2025-07-18T17:07:39.336Z
Learning: Applies to scripts/modules/*.js : Each module in scripts/modules/ should be focused on a single responsibility, following the modular architecture (e.g., commands.js for CLI command handling, task-manager.js for task data and core logic, dependency-manager.js for dependency management, ui.js for CLI output formatting, ai-services-unified.js for AI service integration, config-manager.js for configuration management, utils.js for utility functions).
Applied to files:
package.json
📚 Learning: applies to scripts/modules/*.js : use consistent file naming conventions: 'task_${id.tostring().pads...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/new_features.mdc:0-0
Timestamp: 2025-07-18T17:12:57.903Z
Learning: Applies to scripts/modules/*.js : Use consistent file naming conventions: 'task_${id.toString().padStart(3, '0')}.txt', use path.join for composing file paths, and use appropriate file extensions (.txt for tasks, .json for data).
Applied to files:
package.json
📚 Learning: applies to tests/{unit,integration,e2e,fixtures}/**/*.js : test files must be organized as follows: ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/architecture.mdc:0-0
Timestamp: 2025-07-18T17:07:39.336Z
Learning: Applies to tests/{unit,integration,e2e,fixtures}/**/*.js : Test files must be organized as follows: unit tests in tests/unit/, integration tests in tests/integration/, end-to-end tests in tests/e2e/, and test fixtures in tests/fixtures/.
Applied to files:
package.json
📚 Learning: in the eyaltoledano/claude-task-master repository, agent files are intentionally duplicated between ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1091
File: assets/claude/agents/task-orchestrator.md:1-6
Timestamp: 2025-08-06T21:12:43.673Z
Learning: In the eyaltoledano/claude-task-master repository, agent files are intentionally duplicated between `.claude/agents/` (for internal project use) and `assets/claude/agents/` (as template files for users to copy). This duplication serves different purposes and should be maintained to support both internal development and user distribution needs.
Applied to files:
CHANGELOG.md
📚 Learning: in the eyaltoledano/claude-task-master repository, agent files in assets/claude/agents/ are intended...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1091
File: assets/claude/agents/task-executor.md:1-6
Timestamp: 2025-08-06T21:12:20.956Z
Learning: In the eyaltoledano/claude-task-master repository, agent files in assets/claude/agents/ are intended for distribution to users (for copying), while identical files in .claude/agents/ are for internal project use. This intentional duplication serves different purposes and is not a DRY violation.
Applied to files:
CHANGELOG.md
📚 Learning: commands such as `analyze-complexity`, `expand-task`, `update-task`, and `add-task` should consider ...
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/context_gathering.mdc:0-0
Timestamp: 2025-07-18T17:09:13.815Z
Learning: Commands such as `analyze-complexity`, `expand-task`, `update-task`, and `add-task` should consider adopting the context gathering pattern for improved AI-powered assistance.
Applied to files:
CHANGELOG.md
📚 Learning: for claude agent instruction files in .claude/agents/ and assets/claude/agents/ directories, ignore ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1091
File: assets/claude/agents/task-orchestrator.md:69-78
Timestamp: 2025-08-06T21:13:05.213Z
Learning: For Claude agent instruction files in .claude/agents/ and assets/claude/agents/ directories, ignore markdownlint issues (like MD031 blanks-around-fences, MD040 fenced-code-language, MD041 missing top-level heading) as these files follow Claude's specific agent format requirements rather than standard markdown documentation conventions.
Applied to files:
CHANGELOG.md
📚 Learning: for major feature additions like new cli commands, eyaltoledano prefers detailed changesets with com...
Learnt from: eyaltoledano
PR: eyaltoledano/claude-task-master#1069
File: .changeset/floppy-news-buy.md:7-38
Timestamp: 2025-08-02T14:54:52.216Z
Learning: For major feature additions like new CLI commands, eyaltoledano prefers detailed changesets with comprehensive descriptions, usage examples, and feature explanations rather than minimal single-line summaries.
Applied to files:
CHANGELOG.md
📚 Learning: for files in .claude/agents/ and assets/claude/agents/ directories, ignore markdownlint issues like ...
Learnt from: Crunchyman-ralph
PR: eyaltoledano/claude-task-master#1091
File: .claude/agents/task-orchestrator.md:0-0
Timestamp: 2025-08-06T21:11:37.227Z
Learning: For files in .claude/agents/ and assets/claude/agents/ directories, ignore markdownlint issues like MD041 (missing top-level heading) as these are Claude Code agent instruction files that follow a specific format with YAML frontmatter and don't need to conform to standard markdown documentation conventions.
Applied to files:
CHANGELOG.md
🪛 YAMLlint (1.37.1)
.github/workflows/pre-release.yml
[error] 43-43: trailing spaces
(trailing-spaces)
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md
63-63: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🔇 Additional comments (3)
.changeset/pre.json (1)
2-16: Pre-release metadata looks coherent – no action needed
mode/tagcombination is valid and the changeset list is well-formed (unique IDs, valid JSON).apps/extension/package.json (1)
6-17: Version skew may confuse usersThe extension is now
0.23.1-rc.0while it depends on the core package0.24.0-rc.1.
Once the dependency is switched back to"*", ensure the extension itself is bumped to0.24.xin the follow-up release so versions stay in lock-step.apps/extension/CHANGELOG.md (1)
7-10: Changelog entry looks good – follows project style, includes dependency bump reference.
Comment on lines
+39
to
+56
| # Check if we're in pre-release mode with the "rc" tag | ||
| if [ -f .changeset/pre.json ]; then | ||
| MODE=$(jq -r '.mode' .changeset/pre.json 2>/dev/null || echo '') | ||
| TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '') | ||
|
|
||
| if [ "$MODE" = "exit" ]; then | ||
| echo "Pre-release mode is in 'exit' state, re-entering RC mode..." | ||
| npx changeset pre enter rc | ||
| elif [ "$MODE" = "pre" ] && [ "$TAG" != "rc" ]; then | ||
| echo "In pre-release mode but with wrong tag ($TAG), switching to RC..." | ||
| npx changeset pre exit | ||
| npx changeset pre enter rc | ||
| elif [ "$MODE" = "pre" ] && [ "$TAG" = "rc" ]; then | ||
| echo "Already in RC pre-release mode" | ||
| else | ||
| echo "Unknown mode state: $MODE, entering RC mode..." | ||
| npx changeset pre enter rc | ||
| fi |
Contributor
There was a problem hiding this comment.
🧹 Nitpick (assertive)
Trailing whitespace violates YAML-lint
Static analysis flagged trailing spaces (Line 43 in the raw file).
Remove them to keep the workflow lint-clean.
- TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '')
-
+ TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '')📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| # Check if we're in pre-release mode with the "rc" tag | |
| if [ -f .changeset/pre.json ]; then | |
| MODE=$(jq -r '.mode' .changeset/pre.json 2>/dev/null || echo '') | |
| TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '') | |
| if [ "$MODE" = "exit" ]; then | |
| echo "Pre-release mode is in 'exit' state, re-entering RC mode..." | |
| npx changeset pre enter rc | |
| elif [ "$MODE" = "pre" ] && [ "$TAG" != "rc" ]; then | |
| echo "In pre-release mode but with wrong tag ($TAG), switching to RC..." | |
| npx changeset pre exit | |
| npx changeset pre enter rc | |
| elif [ "$MODE" = "pre" ] && [ "$TAG" = "rc" ]; then | |
| echo "Already in RC pre-release mode" | |
| else | |
| echo "Unknown mode state: $MODE, entering RC mode..." | |
| npx changeset pre enter rc | |
| fi | |
| # Check if we're in pre-release mode with the "rc" tag | |
| if [ -f .changeset/pre.json ]; then | |
| MODE=$(jq -r '.mode' .changeset/pre.json 2>/dev/null || echo '') | |
| TAG=$(jq -r '.tag' .changeset/pre.json 2>/dev/null || echo '') | |
| if [ "$MODE" = "exit" ]; then | |
| echo "Pre-release mode is in 'exit' state, re-entering RC mode..." | |
| npx changeset pre enter rc | |
| elif [ "$MODE" = "pre" ] && [ "$TAG" != "rc" ]; then | |
| echo "In pre-release mode but with wrong tag ($TAG), switching to RC..." | |
| npx changeset pre exit | |
| npx changeset pre enter rc | |
| elif [ "$MODE" = "pre" ] && [ "$TAG" = "rc" ]; then | |
| echo "Already in RC pre-release mode" | |
| else | |
| echo "Unknown mode state: $MODE, entering RC mode..." | |
| npx changeset pre enter rc | |
| fi |
🧰 Tools
🪛 YAMLlint (1.37.1)
[error] 43-43: trailing spaces
(trailing-spaces)
🤖 Prompt for AI Agents
In .github/workflows/pre-release.yml around lines 39 to 56, there are trailing
whitespace characters on line 43 that violate YAML linting rules. Remove any
spaces at the end of line 43 to ensure the YAML file passes lint checks and
maintains clean formatting.
Comment on lines
258
to
260
| "dependencies": { | ||
| "task-master-ai": "*" | ||
| "task-master-ai": "0.24.0-rc.1" | ||
| }, |
Contributor
There was a problem hiding this comment.
Local dependency should use "*" instead of a pinned RC version
Team guidance (see learning dated 2025-08-07) requires intra-monorepo packages to specify "*" so workspace linking is reliable and avoids npm registry look-ups.
Please revert the explicit version.
- "task-master-ai": "0.24.0-rc.1"
+ "task-master-ai": "*"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "dependencies": { | |
| "task-master-ai": "*" | |
| "task-master-ai": "0.24.0-rc.1" | |
| }, | |
| "dependencies": { | |
| - "task-master-ai": "0.24.0-rc.1" | |
| + "task-master-ai": "*" | |
| }, |
🤖 Prompt for AI Agents
In apps/extension/package.json around lines 258 to 260, the dependency
"task-master-ai" is pinned to version "0.24.0-rc.1", but team guidelines require
using "*" for local monorepo dependencies to ensure reliable workspace linking
and avoid npm registry look-ups. Change the version string from "0.24.0-rc.1" to
"*" to comply with this policy.
Comment on lines
+14
to
+41
| ## New Claude Code Agents | ||
|
|
||
| Added specialized agents for Claude Code users to enable parallel task execution, intelligent task orchestration, and quality assurance: | ||
|
|
||
| ### task-orchestrator | ||
|
|
||
| Coordinates and manages the execution of Task Master tasks with intelligent dependency analysis: | ||
| - Analyzes task dependencies to identify parallelizable work | ||
| - Deploys multiple task-executor agents for concurrent execution | ||
| - Monitors task completion and updates the dependency graph | ||
| - Automatically identifies and starts newly unblocked tasks | ||
|
|
||
| ### task-executor | ||
|
|
||
| Handles the actual implementation of individual tasks: | ||
| - Executes specific tasks identified by the orchestrator | ||
| - Works on concrete implementation rather than planning | ||
| - Updates task status and logs progress | ||
| - Can work in parallel with other executors on independent tasks | ||
|
|
||
| ### task-checker | ||
|
|
||
| Verifies that completed tasks meet their specifications: | ||
| - Reviews tasks marked as 'review' status | ||
| - Validates implementation against requirements | ||
| - Runs tests and checks for best practices | ||
| - Ensures quality before marking tasks as 'done' | ||
|
|
Contributor
There was a problem hiding this comment.
🧹 Nitpick (assertive)
Left-aligned headings improve Markdown rendering
Several headings under the “New Claude Code Agents” section are indented by two spaces. While GitHub will still parse them, the indentation breaks most linters (see MD022 / MD024) and makes the document harder to scan.
- ## New Claude Code Agents
+## New Claude Code Agents
...
- ### task-orchestrator
+### task-orchestrator
...
- ### task-executor
+### task-executor
...
- ### task-checker
+### task-checkerRemoving the leading spaces keeps the style consistent with the rest of the changelog and silences markdown-lint errors.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## New Claude Code Agents | |
| Added specialized agents for Claude Code users to enable parallel task execution, intelligent task orchestration, and quality assurance: | |
| ### task-orchestrator | |
| Coordinates and manages the execution of Task Master tasks with intelligent dependency analysis: | |
| - Analyzes task dependencies to identify parallelizable work | |
| - Deploys multiple task-executor agents for concurrent execution | |
| - Monitors task completion and updates the dependency graph | |
| - Automatically identifies and starts newly unblocked tasks | |
| ### task-executor | |
| Handles the actual implementation of individual tasks: | |
| - Executes specific tasks identified by the orchestrator | |
| - Works on concrete implementation rather than planning | |
| - Updates task status and logs progress | |
| - Can work in parallel with other executors on independent tasks | |
| ### task-checker | |
| Verifies that completed tasks meet their specifications: | |
| - Reviews tasks marked as 'review' status | |
| - Validates implementation against requirements | |
| - Runs tests and checks for best practices | |
| - Ensures quality before marking tasks as 'done' | |
| ## New Claude Code Agents | |
| Added specialized agents for Claude Code users to enable parallel task execution, intelligent task orchestration, and quality assurance: | |
| ### task-orchestrator | |
| Coordinates and manages the execution of Task Master tasks with intelligent dependency analysis: | |
| - Analyzes task dependencies to identify parallelizable work | |
| - Deploys multiple task-executor agents for concurrent execution | |
| - Monitors task completion and updates the dependency graph | |
| - Automatically identifies and starts newly unblocked tasks | |
| ### task-executor | |
| Handles the actual implementation of individual tasks: | |
| - Executes specific tasks identified by the orchestrator | |
| - Works on concrete implementation rather than planning | |
| - Updates task status and logs progress | |
| - Can work in parallel with other executors on independent tasks | |
| ### task-checker | |
| Verifies that completed tasks meet their specifications: | |
| - Reviews tasks marked as 'review' status | |
| - Validates implementation against requirements | |
| - Runs tests and checks for best practices | |
| - Ensures quality before marking tasks as 'done' |
🤖 Prompt for AI Agents
In CHANGELOG.md between lines 14 and 41, the headings under "New Claude Code
Agents" are indented by two spaces, which causes markdown-lint errors and
inconsistent style. Remove the leading spaces before these headings so they are
left-aligned, matching the rest of the document and resolving the linting
issues.
Comment on lines
+48
to
+61
| ```bash | ||
| # In Claude Code, after initializing a project with tasks: | ||
|
|
||
| # Use task-orchestrator to analyze and coordinate work | ||
| # The orchestrator will: | ||
| # 1. Check task dependencies | ||
| # 2. Identify tasks that can run in parallel | ||
| # 3. Deploy executors for available work | ||
| # 4. Monitor progress and deploy new executors as tasks complete | ||
|
|
||
| # Use task-executor for specific task implementation | ||
| # When the orchestrator identifies task 2.3 needs work: | ||
| # The executor will implement that specific task | ||
| ``` |
Contributor
There was a problem hiding this comment.
🧹 Nitpick (assertive)
Align code-block fences
The closing fence of the bash block is indented (`␠␠```bash … ␠␠````). Most renderers require the opening and closing fences to start at column 0. Fixing the alignment avoids flaky highlighting and MD031 warnings.
- ```bash
+```bash
...
- ```
+```🤖 Prompt for AI Agents
In CHANGELOG.md around lines 48 to 61, the closing code block fence for the bash
snippet is indented, which can cause rendering issues. Remove the leading spaces
before the closing triple backticks so that both the opening and closing fences
start at column 0, ensuring consistent markdown rendering and avoiding MD031
warnings.
| # The executor will implement that specific task | ||
| ``` | ||
|
|
||
| ## Benefits |
Contributor
There was a problem hiding this comment.
🧹 Nitpick (assertive)
Add blank line before heading (MD022)
The “## Benefits” heading isn’t separated from the preceding code block by a blank line, triggering the CI markdown-lint rule.
- ```
- ## Benefits
+ ```
+
+## BenefitsA single blank line satisfies the rule without affecting visual layout.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Benefits |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
63-63: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
In CHANGELOG.md at line 63, add a blank line before the "## Benefits" heading to
separate it from the preceding code block. This means inserting an empty line
above line 63 so the heading is not immediately after the code block, satisfying
the markdown-lint MD022 rule without changing the visual layout.
…sions (what vscode expects) - chore: run format
Crunchyman-ralph
added a commit
to iamladi/claude-task-master
that referenced
this pull request
Aug 11, 2025
Crunchyman-ralph
added a commit
to iamladi/claude-task-master
that referenced
this pull request
Aug 11, 2025
Merged
16 tasks
stephanschielke
pushed a commit
to stephanschielke/cursor-task-master
that referenced
this pull request
Aug 22, 2025
stephanschielke
pushed a commit
to stephanschielke/cursor-task-master
that referenced
this pull request
Aug 22, 2025
This was referenced Oct 11, 2025
Merged
16 tasks
sfc-gh-dflippo
pushed a commit
to sfc-gh-dflippo/task-master-ai
that referenced
this pull request
Dec 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Description
Related Issues
How to Test This
# Example commands or stepsExpected result:
Contributor Checklist
npm run changesetnpm testnpm run format-check(ornpm run formatto fix)Changelog Entry
For Maintainers
Summary by CodeRabbit
New Features
Bug Fixes
Chores