Use this skill when the user describes a bug (e.g. "users cannot reset password") and you need to identify where in the code the problem might reside.

Goal: Produce a short list of functions, classes or modules that are likely relevant to the bug, so you can focus your debugging efforts.

Shared tool policy:

Follow ../../reference/codegraph-tool-policy.md for common CodeGraph tool selection, fallback and unavailable handling.

Task-specific tools:

Prefer codegraph_search, codegraph_context, codegraph_node, codegraph_callers, codegraph_callees and codegraph_explore for unfamiliar bug areas.

Workflow:

Summarise the bug description into a few keywords (e.g. for "users cannot reset password", keywords might be "password reset", "reset password", "token", "forgotPassword", "resetPassword", etc.).
Ensure the graph index is available using codegraph_status.
Use codegraph_search with these keywords to locate candidate symbols. Include synonyms, route patterns and error messages if possible.
If the bug spans an unfamiliar subsystem, use codegraph_context first. Use codegraph_explore only when you need a deeper survey, and keep the query anchored to symbols or files found by search.
For each candidate, inspect details with codegraph_node and note the file path, symbol kind and any obvious misuse.
Examine callers and callees with codegraph_callers and codegraph_callees to see how the candidate fits into the broader system.
Prioritise candidates based on:
- Direct relationship to the bug keywords (e.g. a resetPassword function)
- Their role in critical flows (authentication, account management)
- Proximity to recent changes (if change history is available)
Compile a ranked list of likely locations with brief explanations. Include file paths, functions/methods and why they are relevant.
Recommend additional investigation steps, such as reading logs, reproducing the bug locally or examining the latest commits touching those areas.

Rules:

Do not attempt to fix the bug within this skill; the goal is to locate relevant code.
Make it clear when the ranking is heuristic and subject to confirmation.
If the graph does not provide enough signal, fall back to simple keyword and directory search and note the limitation.

Más de este repositorio

mismo repositorio

codex-scheduler-watcher

MC-and-his-Agents/MC-SKILLS

创建或更新 Codex meta-scheduler watcher automation。用于为一个项目、milestone、parent issue、issue set、pull request、PR set、release、repo carrier 或手工目标维护 coordination unit graph、scheduler pool、candidate graph/pool、shared lane lock table、scheduler waiting queue 和调度线程生命周期；在安全并行时创建多个 scheduler thread，并在 shared lane 争用时执行 lane grant / wait / release / recovery。默认中文说明和回报，可适配用户语言；协议字段、状态枚举、工具名和结构化模板字段保持机器可读。

2026-06-156

codex-thread-orchestration

MC-and-his-Agents/MC-SKILLS

Codex 线程编排的 scheduler 与 worker 协作协议。用于 Codex 作为 scheduler 拆分全局目标、创建或恢复 worker、管理 branch/worktree、发送跨线程指令、运行 gate、完成 closeout；也用于 Codex 作为 worker 确认分配现场、创建并自检 scoped goal、只执行指定 scope、回报 scheduler-readable 关键节点，并等待 scheduler-owned gate。默认使用中文说明和回报，可根据用户语言适配；协议字段、状态枚举、工具名和结构化模板字段保持机器可读。

2026-06-156

write-a-goal

MC-and-his-Agents/MC-SKILLS

起草、优化或设置符合 OpenAI《Follow a goal》指南的 Codex goal。起草前先根据最新用户请求确定输出语言。为用户起草可复制的单行 /goal 命令；用户明确要求时，通过 goal 工具/API 创建自包含的 active goal objective。用户使用中文、混合语言或语言不明确时，输出中文。保留命令、路径、代码标识符、URL、issue ID、精确引用，以及 /goal、API、objective、copyable_goal_command、active_goal_api 等标识原文。

2026-06-046

architecture-map

MC-and-his-Agents/MC-SKILLS

Map the architecture of a repository using CodeGraph.

2026-05-226

change-plan-with-graph

MC-and-his-Agents/MC-SKILLS

Generate a graph-backed implementation plan before modifying repository code.

2026-05-226

codegraph-context-bootstrap

MC-and-his-Agents/MC-SKILLS

Build repository context using CodeGraph before starting tasks.

2026-05-226

name	bug-localizer
description	Narrow down likely code locations from bug descriptions using CodeGraph.

Use this skill when the user describes a bug (e.g. "users cannot reset password") and you need to identify where in the code the problem might reside.

Goal: Produce a short list of functions, classes or modules that are likely relevant to the bug, so you can focus your debugging efforts.

Shared tool policy:

Follow ../../reference/codegraph-tool-policy.md for common CodeGraph tool selection, fallback and unavailable handling.

Task-specific tools:

Prefer codegraph_search, codegraph_context, codegraph_node, codegraph_callers, codegraph_callees and codegraph_explore for unfamiliar bug areas.

Workflow:

Summarise the bug description into a few keywords (e.g. for "users cannot reset password", keywords might be "password reset", "reset password", "token", "forgotPassword", "resetPassword", etc.).
Ensure the graph index is available using codegraph_status.
Use codegraph_search with these keywords to locate candidate symbols. Include synonyms, route patterns and error messages if possible.
If the bug spans an unfamiliar subsystem, use codegraph_context first. Use codegraph_explore only when you need a deeper survey, and keep the query anchored to symbols or files found by search.
For each candidate, inspect details with codegraph_node and note the file path, symbol kind and any obvious misuse.
Examine callers and callees with codegraph_callers and codegraph_callees to see how the candidate fits into the broader system.
Prioritise candidates based on:
- Direct relationship to the bug keywords (e.g. a resetPassword function)
- Their role in critical flows (authentication, account management)
- Proximity to recent changes (if change history is available)
Compile a ranked list of likely locations with brief explanations. Include file paths, functions/methods and why they are relevant.
Recommend additional investigation steps, such as reading logs, reproducing the bug locally or examining the latest commits touching those areas.

Rules:

Do not attempt to fix the bug within this skill; the goal is to locate relevant code.
Make it clear when the ranking is heuristic and subject to confirmation.
If the graph does not provide enough signal, fall back to simple keyword and directory search and note the limitation.