Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

The manual has no heading answering "can you use skills?", so the chat invents a denial

未关闭
  • 哪里不对？
#1,378 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
documentation, testing-qa

调研方向

Start with the probes in internal/manual/chat_test.go and the skill pages putting-a-skill-in-front.md, use-skill.md, and skills-a-turn-used.md. Add a direct capability heading to the appropriate page covering both enabled and switched-off states, then verify the listed probes fail before the heading exists and pass afterward.

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

描述

area:chat bug sev:papercut

What happened

Asked can you use skills ? on 2f94ca1f0 — a binary carrying the skills wave
(#1365) and its manual pages — the chat answered:

The manual mentions "installed skills" in passing but doesn't explain

and then, after reaching for list_harnesses and list_subharnesses:

If you meant skills in the Claude Code SKILL.md sense, codeaf has no such
mechanism — harnesses and the notebook are what it has instead.

The program denies a feature it ships.

The gap this issue is about

internal/manual/chat_test.go contains no probe mentioning skills. Grepped
the whole table. So the retrieval gate has never once checked that a person's
first question about the newest feature reaches the pages written for it.

The pages themselves are good — putting-a-skill-in-front.md, use-skill.md,
skills-a-turn-used.md. Their headings are:

# Putting a skill in front of this conversation
## How do I use a skill for this
## Attach a skill from any folder
## How do I turn a skill off
# Skills a turn used
## Which skills did it use?
## Did it use my skill?
# use_skill — list or get a skill from the shelf

Every one assumes the asker already knows skills exist. They answer "how do
I use one" and "which did it use". None answers "do you have this at all",
which is the question a person actually asks first, and the one that failed.

This is the failure the manual law names: people search for the word they have,
not the word the writer used. The existing gates pass, because they check that
every tool name and slash command is mentioned somewhere — and use_skill is
mentioned. Mention is not reachability.

Why a correct answer was unreachable in BOTH states

This matters for the fix, because there are two true answers and the corpus has
neither.

On this machine memory.enabled is off, so config.Memory is nil,
useSkillTool (internal/session/tools_skill.go:71) correctly returns nil, and
the verb is absent — the absent-not-broken law working as designed. The true
answer was therefore "skills are switched off on this machine", not "codeaf
has no such mechanism".

With memory on and a populated shelf, the true answer is "yes, here is how".

The corpus has no heading that answers the capability question in either state,
so the model had nothing to retrieve and improvised. A page that cannot be
reached by the question it answers is a page the chat talks over the top of.

Acceptance

  1. Probes in internal/manual/chat_test.go in the asker's own words, including
    verbatim the one that failed:
    • can you use skills
    • do you have skills
    • what is a skill
    • why can't you use my skills
  2. A ## heading that answers the capability question directly, and states the
    refusal as well as the capability — per the manual law, "no, and here is what
    it says instead" is the most useful answer on the page. It has to name the
    switched-off case, because that is a state a person can be in without having
    chosen it knowingly.
  3. The probes fail before the heading exists and pass after. A probe added
    alongside the page that satisfies it proves nothing about retrieval.

Not in scope

Why the shelf is empty on this machine is a separate fault, being handled
elsewhere: memory.enabled off means no store, so discovery records nothing and
renderSkillCatalog emits zero bytes. Whether suppressing that section is right
when it leaves the model with no way to explain itself is also separate. This
issue is only that the corpus cannot answer the question, which is true
independently of both.

主要语言
Go
星标
115
派生
14
平均合并
9 小时 38 分钟
30 天内合并 PR
749

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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