@memo-code/memo 0.7.3 → 0.8.0

package/dist/task-prompts/init_agents.md

@@ -0,0 +1,40 @@
+Generate a file named AGENTS.md that serves as a contributor guide for this repository.
+Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section.
+Follow the outline below, but adapt as needed - add sections if relevant, and omit those that do not apply to this project.
+
+Document Requirements
+
+- Title the document "Repository Guidelines".
+- Use Markdown headings (#, ##, etc.) for structure.
+- Keep the document concise. 200-400 words is optimal.
+- Keep explanations short, direct, and specific to this repository.
+- Provide examples where helpful (commands, directory paths, naming patterns).
+- Maintain a professional, instructional tone.
+
+Recommended Sections
+
+Project Structure & Module Organization
+
+- Outline the project structure, including where the source code, tests, and assets are located.
+
+Build, Test, and Development Commands
+
+- List key commands for building, testing, and running locally (e.g., npm test, make build).
+- Briefly explain what each command does.
+
+Coding Style & Naming Conventions
+
+- Specify indentation rules, language-specific style preferences, and naming patterns.
+- Include any formatting or linting tools used.
+
+Testing Guidelines
+
+- Identify testing frameworks and coverage requirements.
+- State test naming conventions and how to run tests.
+
+Commit & Pull Request Guidelines
+
+- Summarize commit message conventions found in the project's Git history.
+- Outline pull request requirements (descriptions, linked issues, screenshots, etc.).
+
+(Optional) Add other sections if relevant, such as Security & Configuration Tips, Architecture Overview, or Agent-Specific Instructions.

package/dist/task-prompts/review_pull_request.md

@@ -0,0 +1,53 @@
+You are running Memo's dedicated GitHub pull request review workflow.
+
+Target PR number: {{pr_number}}
+Backend strategy (selected by runtime): {{backend_strategy}}
+Backend details: {{backend_details}}
+
+Your job is to perform an end-to-end PR review and publish results directly to GitHub.
+
+Required workflow
+
+1. Connectivity preflight
+
+- First verify the selected backend is usable for this PR operation.
+- If backend preflight fails, stop and explain the exact failure and actionable fix.
+
+2. Load PR context
+
+- Read PR metadata, title, body, changed files, and full diff.
+- Include enough context to evaluate correctness and risk.
+
+3. Perform review
+
+- Focus on: correctness regressions, potential bugs, security risks, API/behavior changes, missing edge-case handling, and maintainability issues.
+- Ignore purely cosmetic style nits unless they hide a bug.
+- Be specific and evidence-based; avoid speculative comments.
+
+4. Publish GitHub review comments
+
+- Post inline review comments for each concrete issue you found.
+- Keep each comment concise and actionable.
+- Use one comment per distinct issue.
+
+5. Publish review summary
+
+- Submit a final PR review summary comment.
+- If no material issues were found, explicitly say so in the summary.
+
+Backend policy
+
+- If backend strategy is `github_mcp`:
+    - Prefer GitHub MCP tools for all GitHub operations.
+    - Prefer tools from the configured server prefix: `{{mcp_server_prefix}}_`.
+    - Do not switch to gh CLI unless MCP path is unavailable and you clearly explain why.
+
+- If backend strategy is `gh_cli`:
+    - Use `exec_command` with GitHub CLI (`gh`) for all GitHub operations.
+    - Do not rely on GitHub MCP tools in this mode.
+
+Result format to user
+
+- Start with a short execution summary: backend used, PR inspected, and whether publishing succeeded.
+- List key findings with file/line references.
+- Confirm what was posted to GitHub (inline comments + final summary), or provide the exact failure reason.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memo-code/memo",
-  "version": "0.7.3",
+  "version": "0.8.0",
   "private": false,
   "type": "module",
   "description": "A lightweight coding agent that runs in your terminal",
@@ -10,6 +10,7 @@
   "files": [
     "dist/index.js",
     "dist/prompt.md",
+    "dist/task-prompts/*.md",
     "README.md",
     "LICENSE"
   ],
@@ -19,6 +20,7 @@
   "devDependencies": {
     "@types/node": "^22.10.2",
     "@types/react": "^19.2.14",
+    "@vitest/coverage-v8": "^2.1.9",
     "prettier": "^3.3.3",
     "tsup": "^8.3.5",
     "tsx": "^4.19.2",
@@ -51,10 +53,11 @@
     "format": "prettier --write \"{packages,site}/**/*.{ts,tsx,js,jsx,mjs,cjs,json,css,mdx}\" \"{package.json,pnpm-workspace.yaml,tsconfig.json,tsup.config.ts,vitest.config.ts,vitest.setup.ts,.prettierrc}\"",
     "format:check": "prettier --check \"{packages,site}/**/*.{ts,tsx,js,jsx,mjs,cjs,json,css,mdx}\" \"{package.json,pnpm-workspace.yaml,tsconfig.json,tsup.config.ts,vitest.config.ts,vitest.setup.ts,.prettierrc}\"",
     "test": "vitest run",
+    "test:coverage": "vitest run --coverage",
     "test:core": "vitest run packages/core",
     "test:tools": "vitest run packages/tools",
     "test:tui": "vitest run packages/tui",
-    "ci": "pnpm run format:check && pnpm run test:core && pnpm run test:tools && pnpm run build",
+    "ci": "pnpm run format:check && pnpm run test:coverage && pnpm run build",
     "release:patch": "npm version patch && npm publish",
     "release:minor": "npm version minor && npm publish",
     "release:major": "npm version major && npm publish"