[agentrc readiness] Level 0 readiness: fix build/test scripts and MCP config

未关闭
#433 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by checking how AgentRC detects build and test scripts and reads MCP configuration; the report does not name the relevant files or entry points. Ask a maintainer to clarify why the app is not detected as having a build script, then inspect the checks for all three gaps. Done means the app passes the build-script, test-script, and MCP-configuration checks on a readiness report rerun.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows automation

Readiness snapshot

Metric Result
Achieved level Level 0 — Functional

Highest-impact gaps

  1. Build script present (0/1 apps) — high impact, low effort. Only 0/1 apps pass this check.
  2. Test script present (0/1 apps) — high impact, low effort. Only 0/1 apps pass this check.
  3. MCP configuration present — high impact, low effort. Missing MCP (Model Context Protocol) configuration (e.g. .vscode/mcp.json or an Agent Plugin mcp.json).

Recommended next step

The report does not name an exact file for the build-script gap. Ask a maintainer to verify why the app is not detected as having a build script, then fix the detection or the script definition so AgentRC passes the "Build script present" check on re-run.

Evidence

  • Deterministic AgentRC readiness report for microsoft/agentrc (workflow run 42167924636).

Generated by AgentRC Readiness Report · copilot · auto · 12.1 AIC · ⌖ 0.509 AIC · ⊞ 4.5K · ◷

  • expires on Nov 20, 2026, 5:25 AM UTC
主要语言
TypeScript
星标
1.1k
派生
96
平均合并
2 天 10 小时
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/agentrc 的其他 Issue

查看 microsoft/agentrc 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。