Bump up to 0.1.3

[yu-iskw]

PR Type

Enhancement

---

Description

• Synchronize monorepo versions to 0.1.3 across all packages

• Add new bumpup-versions skill documentation for version management

• Update CLAUDE.md to reference new version bumping skill

---

Diagram Walkthrough

flowchart LR
  A["Version Bump<br/>0.1.2 → 0.1.3"] --> B["Root package.json"]
  A --> C["All Workspace Packages"]
  A --> D["New Skill Documentation"]
  D --> E["bumpup-versions SKILL.md"]
  E --> F["CLAUDE.md Updated"]

Loading

File Walkthrough

	Relevant files
Documentation	2 files SKILL.md Add comprehensive bumpup-versions skill documentation        +75/-0    CLAUDE.md Register new bumpup-versions skill in skills table              +1/-0
Configuration changes	8 files package.json Bump root package version to 0.1.3                                              +1/-1      package.json Synchronize CLI package version to 0.1.3                                  +1/-1      package.json Synchronize common package version to 0.1.3                            +1/-1      package.json Synchronize core package version to 0.1.3                                +1/-1      package.json Synchronize plugin-api package version to 0.1.3                    +1/-1      package.json Synchronize claude-code-hooks plugin version to 0.1.3        +1/-1      package.json Synchronize cursor-hooks plugin version to 0.1.3                  +1/-1      package.json Synchronize mcp plugin package version to 0.1.3                    +1/-1

---

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Simplify the version bumping process The bumpup-versions skill documentation can be improved by replacing the two separate versioning commands for workspaces and the root with a single, more efficient pnpm -r version command. This simplifies the process and aligns with pnpm best practices for monorepos. Examples: .claude/skills/bumpup-versions/SKILL.md [22-36] ### 2. Synchronize Workspace Packages Run the version command recursively across all packages in the workspace using `pnpm -r exec`. The `--no-git-tag-version` flag prevents automatic git tagging and commits, and `--allow-same-version` ensures it doesn't fail if a package is already at the target version. ```bash pnpm -r exec pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version 3. Update Root Version ... (clipped 5 lines) </details> ### Solution Walkthrough: #### Before: ```markdown # .claude/skills/bumpup-versions/SKILL.md ### 2. Synchronize Workspace Packages ```bash pnpm -r exec pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version 3. Update Root Version pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version 4. Update Lockfile and Internal References pnpm install #### After: ```markdown # .claude/skills/bumpup-versions/SKILL.md ### 2. Synchronize All Package Versions ```bash pnpm -r version <version_or_bump_type> --no-git-tag-version --allow-same-version 3. Update Lockfile and Internal References pnpm install <details><summary>Suggestion importance[1-10]: 8</summary> __ Why: The suggestion correctly identifies a redundant process in the new `bumpup-versions` skill documentation and proposes a more idiomatic, single-command solution, significantly improving the PR's core contribution. </details></details></td><td align=center>Medium </td></tr><tr><td rowspan=1>General</td> <td> <details><summary>Use a robust pnpm command</summary> ___ **In the verification step of the <code>bumpup-versions</code> skill, replace the brittle <code>grep</code> <br>command with the more robust <code>pnpm m ls</code> to list all workspace packages and their <br>versions.** [.claude/skills/bumpup-versions/SKILL.md [46-52]](https://github.com/yu-iskw/coding-agent-fabric/pull/15/files#diff-9d3d4bbf6b93a295e13e587771d328e8971d3a595ad11df6a5dac0dfab6db2faR46-R52) ```diff ### 5. Verify Changes -Check a sample of `package.json` files to ensure they all reflect the new version. +List all workspace packages and their versions to ensure they all reflect the new version. ```bash -grep '"version":' package.json packages/*/package.json packages/plugins/*/package.json +pnpm m ls - [ ] **Apply / Chat** <!-- /improve --apply_suggestion=1 --> <details><summary>Suggestion importance[1-10]: 6</summary> __ Why: The suggestion correctly identifies that the `grep` command is brittle due to hardcoded paths and proposes using `pnpm m ls`, which is a more robust and idiomatic way to verify package versions in a pnpm workspace. </details></details></td><td align=center>Low </td></tr> <tr><td align="center" colspan="2"> - [ ] More <!-- /improve --more_suggestions=true --> </td><td></td></tr></tbody></table>