mxsm / mxsm/rocketmq-rust

[Bug🐛] Fix unresolved glossary paths in translation skills

Closed Beginner friendly
#10,752 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug🐛
Dominant language
Rust
Stars
1.5k
Forks
264
Avg merge
1h 34m
Merged PRs (30d)
567

Description

Prerequisites
  • I have searched existing issues and discussions
  • This is a bug, not a question (use Discussions for questions)
Environment
  • OS:
  • RocketMQ Rust:
  • Rust:
Bug Description

Both repository-scoped copies of the translate-it-doc-en-zh skill declare six mandatory glossary files using ../glossary/... paths:

  • .agents/skills/translate-it-doc-en-zh/SKILL.md
  • .claude/skills/translate-it-doc-en-zh/SKILL.md

Relative to either SKILL.md directory, those paths resolve under .agents/skills/glossary/ or .claude/skills/glossary/. Neither directory exists. The tracked glossary files are under .agents/glossary/ and .claude/glossary/, one additional level above the declared locations.

As a result, an agent following the skill cannot resolve the mandatory terminology files reliably, so the skill's glossary constraints may not be applied.

Steps to Reproduce

No response

Expected vs Actual

No response

Logs/Screenshots

No response

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading .agents/skills/translate-it-doc-en-zh/SKILL.md and .claude/skills/translate-it-doc-en-zh/SKILL.md, then compare their six glossary references with the files under .agents/glossary/ and .claude/glossary/. Done means every mandatory glossary path resolves from its corresponding SKILL.md location in both copies.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, localization
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.