Skip to content

Clarify README search discovery#23

Merged
dd3ok merged 1 commit into
mainfrom
codex/readme-search-discovery
Jun 10, 2026
Merged

Clarify README search discovery#23
dd3ok merged 1 commit into
mainfrom
codex/readme-search-discovery

Conversation

@dd3ok

@dd3ok dd3ok commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • clarify the English and Korean README introductions with AgentSkills-compatible wording and core runtime names
  • add English and Korean audience sections for users who need lightweight Markdown deferred-check tracking
  • keep scheduler/reminder negative-scope language covered by tests

Metadata

  • kept repository topics concise and added only ai-agent, claude-code, and markdown
  • did not add GitHub Pages or profile README changes

Testing

  • python -m unittest discover -s evals -p test_*.py
  • python evals/check_release_metadata.py
  • python evals/check_policy_markers.py
  • python evals/check_semantic_cases.py
  • python evals/check_skill_package.py
  • git diff --check

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the English and Korean README files to clarify the project's introduction and target audience, adds a corresponding unit test to verify these changes, and updates the changelog. The review feedback suggests a minor phrasing improvement in the Korean translation to maintain a professional tone.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread README.ko.md

## 누구를 위한 도구인가요?

AI agent workflow를 만들거나 운영하면서 scheduler, daemon, database, MCP server를 만들지 않고 deferred check, CI 후속 확인, 배포 검증, PR 확인, 티켓, 작업, 데이터 동기화, 이메일 후속 확인을 가벼운 Markdown 방식으로 추적해야 한다면 WATCHLIST.md가 맞습니다.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase WATCHLIST.md가 맞습니다 (literally "WATCHLIST.md is correct") sounds a bit colloquial and literal in Korean technical documentation. Using a more professional and natural term like WATCHLIST.md가 적합합니다 (is suitable) or WATCHLIST.md가 제격입니다 (is ideal) would better align with the formal tone used throughout the rest of the document.

Suggested change
AI agent workflow를 만들거나 운영하면서 scheduler, daemon, database, MCP server를 만들지 않고 deferred check, CI 후속 확인, 배포 검증, PR 확인, 티켓, 작업, 데이터 동기화, 이메일 후속 확인을 가벼운 Markdown 방식으로 추적해야 한다면 WATCHLIST.md가 맞습니다.
AI agent workflow를 만들거나 운영하면서 scheduler, daemon, database, MCP server를 만들지 않고 deferred check, CI 후속 확인, 배포 검증, PR 확인, 티켓, 작업, 데이터 동기화, 이메일 후속 확인을 가벼운 Markdown 방식으로 추적해야 한다면 WATCHLIST.md가 적합합니다.

@dd3ok dd3ok merged commit ac34139 into main Jun 10, 2026
4 checks passed
@dd3ok dd3ok deleted the codex/readme-search-discovery branch June 10, 2026 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant