Buscar habilidades.../

Archivo del skill

Open Files First Targeting

Identify the most likely files to edit for bug-fix or modification requests by prioritizing currently open files and their related component files before broad repository search. Use when the user asks to fix or modify behavior without precise file paths, especially when editor-open files are available.

0 estrellas

23 mar 2026

Ocupación
Categorías: Base de Conocimientos

Contenido de la habilidad

Use this workflow to reduce wrong-file edits and speed up fixes.

Workflow

Collect candidate files from open context first.

Treat editor-open files and files recently shown in the thread as top-priority candidates.
If the user mentions a page/feature, keep only open files in that feature subtree.
For each open file, collect related component files first (component .ts, .html, .scss, plus nearest service/module/routing files in the same feature).

Build a ranked target list before editing.

Rank highest: open files with matching component/service names, error keywords, route names, or symbols from the request.
Rank second: related component files for those open files (*.component.ts, *.component.html, *.component.scss, feature service, module, routing).
Rank third: broader repo matches from targeted rg search.

Verify quickly before patching.

Confirm at least one concrete link from request to file: request keyword match, symbol reference, stack trace mention, or template binding.

Skills relacionados

Instalación rápida

Open Files First Targeting

npx skills add Ykhali/codex_skills

Descargar Skill Abrir repositorio

Autor: Ykhali
estrellas: 0
Actualizado: 23 mar 2026
Ocupación

En esta página

If confidence is low, run one focused search rather than broad refactor.

Edit minimally in the highest-confidence file first.

Apply one small fix.
Re-check behavior or run the smallest useful validation.
Expand to second-ranked files only if needed.

Report targeting rationale in handoff.

State why edited files were chosen (for example: "file was open and matched error symbol").

Fallback Rules

If no open files are available, start from route/page mapping, then template -> component -> service chain.
If multiple open files conflict (different features), ask one short clarification question before editing.
Never assume broad refactor is needed when one open-file path explains the bug.
For modify/fix requests, do not start broad global search until open files and their component neighbors are checked.

02

Fallback Rules

Desarrolladores de software

CMS y Plataformas

Notion

Notion API for creating and managing pages, databases, and blocks.

Base de Conocimientos

Feishu Wiki

Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.

Base de Conocimientos

Gemini

Gemini CLI for one-shot Q&A, summaries, and generation.

Base de Conocimientos

Obsidian Vault Maintainer

Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.

Base de Conocimientos

Openclaw Pr Maintainer

Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.

Base de Conocimientos

Wiki Maintainer

Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

Desarrolladores de software

Open Files First Targeting | Skills Pool