القائمة
Rename or refactor a symbol safely by searching every naming-case variant across code, tests, docs, configs, and JSON. Use when renaming any identifier so no reference is missed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement a GitHub issue step by step - ask about the branch, the PR target, and the phases first, then run the work and the review cycle with the review-pr skill. Use whenever the user asks to implement, work on, or execute a GitHub issue.
Create a well-structured GitHub issue with duplicate detection, code verification, and auto-labeling. Use whenever the user asks to create, file, open, log, or raise a GitHub issue, in any wording.
Review a GitHub pull request and post one clear review, with inline comments. The default is collaborative - you analyze deeply, explain the changes in simple terms, ask the user about each finding, and post a review that reflects their decisions. Use when the user asks to review a PR. --no-verdict = programmatic COMMENT-only mode that also writes .reviews/<PR_NUMBER>-review.md (used by implement-issue). --autonomous = unattended review that posts a formal verdict.
Root-cause a bug or a failed fix with evidence, not guesses - brainstorm causes, research them in parallel, confirm one with logs before changing code. Use when a reported behavior needs root-causing or a fix attempt has failed.
Author or edit AI-facing instruction files in this repo - AGENTS.md, skills under .claude/skills/, subagents under .claude/agents/, and spawned-agent prompts. Covers the prompt-writing rules for current Claude models, the map-not-manual standard for AGENTS.md, the living-document rule, and when and where to persist a new rule. Use when editing any AI-instruction file.
Scaffold a new web-project with folder, README, tests, portfolio data, ADRs, and documentation updates
| name | rename-symbol |
| description | Rename or refactor a symbol safely by searching every naming-case variant across code, tests, docs, configs, and JSON. Use when renaming any identifier so no reference is missed. |
When you rename or refactor any symbol, search all naming variants (camelCase, PascalCase, snake_case, kebab-case, UPPER_CASE) across the whole project (code, tests, docs, configs, and JSON), not just the obvious code references. This repo has no compiler, so a missed variant does not fail a build: it loads fine and then breaks at runtime in the browser. A missed variant in a config key or a data file is the usual cause.
Extra traps in this repo:
data/ are a schema. Portfolio project fields conform to data/schemas/project.schema.json. Renaming a field means updating the schema, every data/projects/*.json file, and the rendering code together (the CI data-validation test catches drift).sitemap.xml and the <!-- BEGIN GENERATED:<NAME> --> ... <!-- END GENERATED:<NAME> --> blocks in index.html and web-projects/index.html derive from data/ (root ADR 0010). If a renamed name feeds them, re-run bun scripts/generateSitemap.js and bun scripts/generateSeoBlocks.js, then confirm no stale name remains (CI drift tests fail otherwise).marked is imported by name via the esm.sh CDN (root ADR 0005); a rename there must match the import. Filter IDs are derived: idFromText() in js/utils/textUtils.js strips punctuation/spaces and capitalizes to build element IDs and filter matches, so renaming a type or skill string changes its derived ID everywhere it is matched.