@mesrai/cli 0.4.21

package/skills/mesrai-mesrai-rules/rules/update-mesrai-rule.md

@@ -0,0 +1,55 @@
+---
+name: update-mesrai-rule
+description: Mesrai Rule Update Guidelines - Use when the user wants to update an existing Mesrai Rule to modify its behavior, scope, or severity for Mesrai to follow when generating code.
+---
+
+# Mesrai Rule Update Guidelines
+
+## Overview
+
+When updating an existing Mesrai Rule, it's important to ensure that the changes are clear, justified, and aligned with the overall goals of code generation. Updating a Mesrai Rule can help refine its effectiveness and ensure that it continues to meet the user's expectations and project requirements.
+
+## Workflow for Updating a Mesrai Rule
+
+1. **Identify the Mesrai Rule to Update**:
+    - If the user specified a specific `uuid` of the Mesrai Rule they want to update, use it to identify the rule.
+    - If the user described the rule to update without providing a `uuid`, list all rules (or filter by repository if specified), select the most relevant one based on the description, and confirm with the user that this is the correct rule to update before proceeding.
+    - Otherwise, ask the user to specify the rule they want to update by providing its `uuid` or a clear description that can be used to identify it. Emphasize that `uuid` is the most reliable way to identify the rule for updating.
+
+2. **Collect the user's intent for the update**: Understand the specific changes the user wants to make to the existing Mesrai Rule. Ask clarifying questions if necessary to ensure you have a clear understanding of the user's intent.
+
+3. **Review the existing Mesrai Rule**: Retrieve the current definition of the Mesrai Rule that is being updated. This will help you understand the existing behavior and identify what changes need to be made.
+
+4. **Draft the updated Mesrai Rule**: Based on the user's intent and the existing rule, draft an updated version of the Mesrai Rule that includes the desired changes. Use the guidelines outlined in the "Guidelines for Updating a Mesrai Rule" section to ensure the updated rule is well-structured and effective.
+
+5. **Review the updated Mesrai Rule with the user**: Present the drafted updated Mesrai Rule to the user for feedback. Discuss any potential edge cases, exceptions, or clarifications needed to ensure the updated rule is comprehensive and actionable.
+
+6. **Refine the updated Mesrai Rule**: Based on the user's feedback, refine the updated Mesrai Rule to address any concerns or suggestions. Ensure that the final version of the updated rule is clear, specific, and aligned with the user's goals.
+
+7. **Save and Implement the updated Mesrai Rule**: Once the updated Mesrai Rule is finalized and approved by the user, save it. Send only the fields that were updated, along with the `uuid` to identify which rule to update.
+
+Use the following command to save the updated Mesrai Rule:
+
+```
+mesrai rules update --uuid <uuid> [--repo-id <repository-id>] [--title <title>] [--rule <rule-content>] [--severity <severity-level>] [--scope <scope-level>] [--path <glob-pattern>]
+```
+
+8. **Communicate the updated Mesrai Rule**: Inform the user about the updated Mesrai Rule and how the changes will affect future code generation.
+
+## Centralized Config Behavior
+
+When centralized config is enabled, updating a rule may return centralized PR metadata instead of an immediate rule update.
+
+In this case, report PR details and clarify the update is pending until PR merge and sync.
+
+## Guidelines for Updating a Mesrai Rule
+
+1. **Identify the Changes**: Clearly define what changes are being made to the existing Mesrai Rule. Are you modifying the rule's behavior, scope, severity, or other attributes?
+
+2. **Justify the Changes**: Ensure that there is a clear justification for the changes being made to the Mesrai Rule. The updates should contribute to producing code that is more maintainable, efficient, or better aligned with the user's needs.
+
+3. **Consider Edge Cases**: Think about any edge cases or exceptions that might arise from the updated rule. Address these in the updated rule definition to ensure Mesrai can handle them appropriately.
+
+4. **Align with Project Goals**: Ensure that the updated Mesrai Rule continues to align with the overall goals and requirements of the project. The updated rule should contribute to producing code that meets the user's expectations and project requirements.
+
+5. **Review and Refine**: After drafting the updated Mesrai Rule, review it for clarity and completeness. Present it to the user for feedback and refine it as necessary to ensure it effectively guides Mesrai's code generation process.

package/skills/mesrai-mesrai-rules/rules/view-mesrai-rules.md

@@ -0,0 +1,56 @@
+---
+name: view-mesrai-rules
+description: Mesrai Rule Viewing Guidelines - Use when the user wants to view existing Mesrai Rules that Mesrai follows when generating code.
+---
+
+# Mesrai Rule Viewing Guidelines
+
+## Overview
+
+When viewing existing Mesrai Rules, it's important to understand the details of each rule, including its UUID, title, rule content, severity, scope, and any applicable file patterns. This information helps you understand how Mesrai generates code and what guidelines it follows.
+
+## Workflow for Viewing Mesrai Rules
+
+1. **Retrieve Rule Target**: Specific rules can be retrieved by their `uuid`. Otherwise you can list all rules or filter them by their `repositoryId`.
+   This can be achieved with the following options:
+    - `--uuid <uuid>`
+    - `--repo-id <repository-id>`
+
+2. **Fetch Mesrai Rules**: Use the appropriate command to fetch the Mesrai Rule(s) based on the identified target(s). If no specific rule was requested, fetch all existing Mesrai Rules.
+
+Use the following command to fetch Mesrai Rules:
+
+```
+mesrai rules view [--repo-id <repository-id>] [--uuid <uuid>]
+```
+
+3. **Display Mesrai Rules**: Present the retrieved Mesrai Rule(s) in a clear and organized manner. For each rule, display the following information:
+    - Rule UUID
+    - Repository ID
+    - Rule Title
+    - Rule
+    - Severity
+    - Scope
+    - Path
+
+Do not alter the content of the rules; display them as they are retrieved to ensure accuracy.
+
+4. **Provide Context**: If the user is viewing a specific rule, provide additional context about how that rule is applied in code generation and any relevant examples or use cases.
+
+5. **Answer Follow-up Questions**: Be prepared to answer any follow-up questions the user may have about the Mesrai Rules, such as how to create or update rules, or how specific rules affect code generation.
+
+## Centralized Config Context
+
+When centralized config is enabled, rules may include centralized pending state metadata.
+
+When relevant, surface centralized path and status, and clarify that pending centralized changes apply only after PR merge and sync.
+
+## Guidelines for Viewing Mesrai Rules
+
+1. **Be Accurate**: When displaying Mesrai Rules, ensure that the information is accurate and reflects the current state of the rules as retrieved from the system.
+
+2. **Be Clear**: Present the Mesrai Rules in a clear and organized manner, making it easy for the user to understand the details of each rule.
+
+3. **Provide Context**: When appropriate, provide additional context about how specific Mesrai Rules are applied in code generation and how they affect the output.
+
+4. **Be Responsive**: Be prepared to answer any follow-up questions the user may have about the Mesrai Rules, and provide helpful information to guide them in understanding and utilizing the rules effectively.

package/skills/mesrai-pr-suggestions-resolver/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: mesrai-pr-suggestions-resolver
+description: Use when the user wants to fetch, triage, or implement Mesrai suggestions for an existing remote pull request via `mesrai pr suggestions`, `--pr-url`, or `--pr-number`.
+---
+
+# Mesrai PR Suggestions Resolver
+
+## Overview
+
+Fetch PR suggestions via Mesrai CLI, triage each suggestion against the PR goal, apply safe fixes, then validate with build/tests and report results.
+
+## Workflow
+
+### 1) Collect the PR target
+
+- If the user did not provide a target, ask for one of:
+    - `--pr-url <url>`
+    - `--pr-number <number>` with `--repo-id <id>`
+- If multiple are provided, prefer `--pr-url`.
+
+### 2) Run Mesrai suggestions
+
+Use:
+
+```
+mesrai pr suggestions --pr-url <url>
+```
+
+Or when the URL is not available:
+
+```
+mesrai pr suggestions --pr-number <number> --repo-id <id>
+```
+
+### 3) Analyze suggestions with PR intent in mind
+
+- Extract or confirm the PR goal from the user or PR context.
+- For each suggestion:
+    - Verify it does not conflict with the PR objective.
+    - Prefer small, low-risk changes that improve the PR without changing scope.
+    - Skip suggestions that are irrelevant, risky, or scope-expanding; note why.
+
+### 4) Apply fixes one by one
+
+- Make changes per accepted suggestion.
+- Keep edits minimal and focused.
+- If a suggestion is unclear, ask a clarifying question before changing code.
+
+### 5) Validate with build/tests (when available)
+
+- Run the most relevant build or tests for the edited area.
+- If no tests are available or running them is not possible, state that explicitly.
+
+### 6) Report results
+
+Provide a concise report covering:
+
+- Suggestions applied (with brief rationale).
+- Suggestions skipped (with reasons).
+- Tests/builds run and outcomes.
+- Remaining uncertainties or follow-ups needed.

package/skills/mesrai-review/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: mesrai-review
+description: Use when the user wants Mesrai to review local changes, run `mesrai review` or `--prompt-only`, fix Mesrai review findings, or check commit, push, or merge readiness.
+---
+
+# Mesrai Review
+
+## Goal
+
+Use the Mesrai CLI to review changes and resolve issues. Prefer machine-friendly output via `--prompt-only`, then apply fixes in code.
+
+If the request is to validate local changes against business rules, task requirements, or acceptance criteria, use `mesrai-business-rules-validation` instead. `mesrai review` does not trigger local business validation.
+
+## Trigger Hints
+
+- Treat mentions of `review`, `commit`, `push`, `open PR`, `merge`, `quality gate`, or `ready to ship` as triggers for this skill.
+- For commit/push/merge requests, proactively ask to run Mesrai review first when a fresh review has not run yet in the current task.
+
+## Workflow
+
+1. Ensure Mesrai CLI is available.
+
+- Run `mesrai --help` to confirm.
+- If missing, ask the user to install the CLI and stop.
+
+2. Ensure authentication if required.
+
+- If `mesrai review` fails with auth, ask the human to authenticate with `mesrai auth login` in their terminal, then retry after they confirm.
+- For team keys, use `mesrai auth team-key --key <key>` when provided by the user.
+
+3. Run review using prompt-only output.
+
+- Default: `mesrai review --prompt-only`.
+- If user specifies files: `mesrai review --prompt-only <files...>`.
+- If user asks for staged/commit/branch: add `--staged`, `--commit <sha>`, or `--branch <name>`.
+- If user wants fast: add `--fast`.
+
+4. Parse results and apply fixes.
+
+- Use the output to locate files and lines.
+- Make minimal, targeted changes to address each issue.
+- If an issue is not actionable or is a false positive, explain why and skip.
+
+5. Re-run review if needed.
+
+- After fixes, rerun `mesrai review --prompt-only` to confirm issues are resolved.
+
+## Notes
+
+- Prefer `--prompt-only` for predictable parsing.
+- Avoid `--interactive` unless the user explicitly asks.
+- Redirect PR-vs-task validation requests to `mesrai-business-rules-validation`.
+- Use `review --help` to undertstand review possibilities

package/skills/mesrai-review-dev/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: mesrai-review-dev
+description: Use when the user wants Mesrai to review local changes through a local CLI build or non-production API such as `node dist/index.js`, localhost, or QA, including local `--prompt-only` flows.
+---
+
+# Mesrai Review (Dev)
+
+## Goal
+
+Use the local Mesrai CLI build in this repository to review changes and resolve issues. Prefer machine-friendly output via `--prompt-only`, then apply fixes in code.
+
+If the request is to validate local changes against business rules, task requirements, or acceptance criteria, use `mesrai-business-rules-validation` instead. The local review command does not trigger local business validation.
+
+## Trigger Hints
+
+- Treat mentions of `review`, `commit`, `push`, `open PR`, `merge`, `quality gate`, or `ready to ship` as triggers for this skill.
+- For commit/push/merge requests, proactively ask to run local Mesrai review first when a fresh review has not run yet in the current task.
+
+## Workflow
+
+1. Ensure local dev command is available.
+
+- Prefer the helper script (do not rely on aliases).
+- Use: `skills/mesrai-review-dev/scripts/run-local-cli.sh --help`.
+- If missing or failing, ask the user to confirm the local path and env values, then stop.
+
+2. Ensure authentication if required.
+
+- If the review fails with auth, ask the human to authenticate with `mesrai auth login` in their terminal, then retry after they confirm.
+- For team keys, use `auth team-key --key <key>` with the same helper script when provided by the user.
+
+3. Run review using prompt-only output.
+
+- Default: `skills/mesrai-review-dev/scripts/run-local-cli.sh review --prompt-only`.
+- If user specifies files: append `<files...>`.
+- If user asks for staged/commit/branch: add `--staged`, `--commit <sha>`, or `--branch <name>`.
+- If user wants fast: add `--fast`.
+
+4. Parse results and apply fixes.
+
+- Use the output to locate files and lines.
+- Make minimal, targeted changes to address each issue.
+- If an issue is not actionable or is a false positive, explain why and skip.
+
+5. Re-run review if needed.
+
+- After fixes, rerun `skills/mesrai-review-dev/scripts/run-local-cli.sh review --prompt-only` to confirm issues are resolved.
+
+## Notes
+
+- Prefer `--prompt-only` for predictable parsing.
+- Avoid `--interactive` unless the user explicitly asks.
+- Redirect PR-vs-task validation requests to `mesrai-business-rules-validation`.
+- The helper script respects `MESRAI_API_URL`, `MESRAI_VERBOSE`, and `MESRAI_CLI_ENTRYPOINT`.
+- Do not use `--fix` unless the user explicitly asks.

package/skills/mesrai-review-dev/scripts/run-local-cli.sh

@@ -0,0 +1,49 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+script_dir="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
+repo_root="$(cd -- "${script_dir}/../../.." && pwd)"
+
+entrypoint="${MESRAI_CLI_ENTRYPOINT:-${repo_root}/dist/index.js}"
+api_url="${MESRAI_API_URL:-http://localhost:3001}"
+verbose="${MESRAI_VERBOSE:-1}"
+
+print_help() {
+  cat <<EOF
+Run the local Mesrai CLI build from this repository.
+
+Usage:
+  $(basename "$0") <command> [args...]
+
+Environment:
+  MESRAI_API_URL         Defaults to http://localhost:3001
+  MESRAI_VERBOSE         Defaults to 1
+  MESRAI_CLI_ENTRYPOINT  Defaults to <repo>/dist/index.js
+
+Examples:
+  $(basename "$0") --help
+  $(basename "$0") auth status
+  $(basename "$0") review --prompt-only
+EOF
+}
+
+if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then
+  print_help
+  exit 0
+fi
+
+if [[ $# -eq 0 ]]; then
+  print_help
+  exit 1
+fi
+
+if [[ ! -f "$entrypoint" ]]; then
+  echo "Local Mesrai CLI entrypoint not found: $entrypoint" >&2
+  echo "Run 'npm run build' in ${repo_root} or set MESRAI_CLI_ENTRYPOINT." >&2
+  exit 1
+fi
+
+exec env \
+  MESRAI_API_URL="$api_url" \
+  MESRAI_VERBOSE="$verbose" \
+  node "$entrypoint" "$@"