CommandCodeAI / CommandCodeAI/command-code

Taste.md adds lot of redundant info which leads to low quality code

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

还没有人认领这个 Issue。

p2
主要语言
没有语言数据
星标
4k
派生
350
PR 合并指标
30 天内没有已合并 PR

描述

Summary

If projects is being built using AI, it evolves rapidly within a week. Taste fails to update obsolete info and leads to conflicting statements. This causes lower quality code and token burn.

Expected Behavior

Taste should update dynamically- not even add new info but also replace older, outdated info.

Actual Behavior
  1. Attached taste.md from a Wordpress project I started working on. It has obsolete info about initial scaffolding struggles. Also refer the QA video from Github Copilot. The project has moved to building custom plugins and themes within days, the taste.md has become obsolete.
  2. Attached another file it created under commandcode/workflow/taste.md.

taste (1).md
taste.md
https://github.com/user-attachments/assets/a3e2f726-d2c7-4990-9093-97f5d25bbe2c

Note in initial scaffolding I setup puppeteer, then moved to playwright mcp and removed puppeteer. But taste.md still asks to use puppeteer >> more confusion >> lower quality code.

Steps to reproduce the issue

Move a project rapidly from one stage to another and watch whether taste is able to replace obsolete info.

Command Code Version

0.26.8

Operating System

Linux

Terminal/IDE

vscode

Shell

bash

Additional context

My env is WSL-Ubuntu

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

调研方向

先比较附加的 taste.md 文件,尤其是过时的 Puppeteer 指南与后来的 Playwright MCP 设置,并追踪 commandcode/workflow/taste.md 在何处生成或更新。完成标准应包括一次可复现的项目迁移,其中用新的指导替换过时的指导,而不是保留它们,从而使生成的 taste.md 不再给出相互冲突的指示。

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

评估

技术栈
playwright
领域
ai, cli, tooling
Issue 类型
缺陷
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
42/100

把新 issue 发到你的邮箱

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