repo-map-codex

Étoiles18

Forks1

Mis à jour20 juillet 2026 à 12:04

Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

dachent

dachent/skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

7 fichiers

SKILL.md

readonly

name	repo-map-codex
description	Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection.

Codex Repo Map

Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection. Do not use this package for new work.

Overview

Create a durable map of the project so later planning is grounded in evidence rather than memory. The map adapts to software with Git, software without Git, business artifact work, and mixed business-coding projects.

Workflow

Determine the project mode: software-git, software-no-git, business-artifact, or mixed-business-coding.
Explore read-only first. Prefer rg --files, rg, normal file reads, and parallel reads with multi_tool_use.parallel when available.
Build a concise repo-map.md or equivalent project map.
Build an evidence-catalog.md that lists source materials, attempt/outcome status, and relevance.
Record unknowns separately from facts. Do not ask the user for facts that can be discovered.

When Invoked By deep-planning-codex

Use the orchestrator-selected project mode unless discovered evidence contradicts it. If the mode changes, record the reason in .deep-planning/project-mode.md.
Write .deep-planning/repo-map.md and .deep-planning/evidence-catalog.md using the deep-planning artifact contract. The evidence catalog must include Failure mechanism for failed, partial, stale, or unreached evidence.
Use N/A in Failure mechanism for successful evidence rows.
End with a Deep Planning Delta for the orchestrator to merge into .deep-planning/state.md. Use READY_FOR_PROCEED only when the map and evidence catalog are complete enough for the next planning phase.
If required evidence is missing, set status to BLOCKED_BY_MISSING_EVIDENCE and make Next action name the exact source, access, or probe needed.

Mode References

Read the relevant reference before writing the map:

references/software-git.md
references/software-no-git.md
references/business-artifact.md
references/mixed-business-coding.md

Minimum Output

The map must include:

project mode and why it was selected;
key source materials;
entrypoints or primary deliverables;
relevant commands, if any;
source-of-truth data/docs;
dependencies and external systems;
generated or derived artifacts;
validation surfaces;
risk areas;
unknowns that require user or stakeholder input.

Write Scope

When used inside deep planning, write only to the target project's .deep-planning/repo-map.md and .deep-planning/evidence-catalog.md unless the user specifies another planning workfolder.

Plus depuis ce dépôt

même dépôt

xlsx-win

dachent/skills

native microsoft excel automation for windows .xlsx/.xlsm/.xls/.csv/.tsv workflows. use when chatgpt, codex, or claude code is running on windows with microsoft 365 excel installed and needs to refresh, recalculate, validate, or route a workbook through excel com automation. trigger for workbook connections, cached values, pivottables, calculation correctness, refreshing an existing power query connection, data model-aware routing, chart-ready data, no-template spreadsheet deliverables, or excel environment self-test. does not support authoring or editing power query m code, or macro execution -- see "known gaps" below. do not use for cloud execution, non-windows environments, google sheets api workflows, or machines without excel desktop installed.

2026-08-0218

agent-project-orchestrator

dachent/skills

Archived. Do not install or invoke for Claude Code or Codex GPT-5.6 Sol. Use the repository's scaffolds/agent-project-scaffold for the maintained scaffold or native Codex planning and execution controls.

2026-07-2718

document-handoff

dachent/skills

Create a comprehensive project archive and handoff package — curated workfolder copy, evidence and state, agent context, and dark-mode HTML memo — from Claude Code or Codex projects. Use for milestone archives, cold-start continuation packages, or comprehensive handoffs; use a lightweight session-handoff skill for a short continuation note.

2026-07-2418

code-intelligence

dachent/skills

use only in Claude Code as an explicit provider router when Graphify, code-mapper, or selective CodeQL availability must be assessed. do not install or auto-trigger for Codex GPT-5.6 Sol; native direct inspection, Plan Mode, explorer work, and subagents cover this routing without an added analyzer.

2026-07-2018

code-mapper-skill

dachent/skills

Generate deterministic Python import, reference, artifact, contract, catalog, OpenLineage, and explicitly authorized local CodeQL maps. Use for explicit Python blast-radius, callers, inputs/outputs, APIs/schemas, Backstage relationships, lineage, or local value/taint evidence; do not use for ordinary code search, broad repository exploration, or simple edits.

2026-07-2018

deep-planning-codex

dachent/skills

Deprecated for GPT-5.6 Sol. Use native Codex Plan Mode, with focused verification or adversarial review skills when needed.

2026-07-2018

Codex Repo Map

Deprecated for GPT-5.6 Sol. Native Codex Plan Mode performs read-first repository grounding and evidence collection. Do not use this package for new work.

Overview

Workflow

Determine the project mode: software-git, software-no-git, business-artifact, or mixed-business-coding.

Explore read-only first. Prefer rg --files, rg, normal file reads, and parallel reads with multi_tool_use.parallel when available.

Build a concise repo-map.md or equivalent project map.

Build an evidence-catalog.md that lists source materials, attempt/outcome status, and relevance.

Record unknowns separately from facts. Do not ask the user for facts that can be discovered.

When Invoked By deep-planning-codex

Use the orchestrator-selected project mode unless discovered evidence contradicts it. If the mode changes, record the reason in .deep-planning/project-mode.md.

Write .deep-planning/repo-map.md and .deep-planning/evidence-catalog.md using the deep-planning artifact contract. The evidence catalog must include Failure mechanism for failed, partial, stale, or unreached evidence.

Use N/A in Failure mechanism for successful evidence rows.

End with a Deep Planning Delta for the orchestrator to merge into .deep-planning/state.md. Use READY_FOR_PROCEED only when the map and evidence catalog are complete enough for the next planning phase.

If required evidence is missing, set status to BLOCKED_BY_MISSING_EVIDENCE and make Next action name the exact source, access, or probe needed.

Mode References

Read the relevant reference before writing the map:

references/software-git.md

references/software-no-git.md

references/business-artifact.md

references/mixed-business-coding.md

Minimum Output

The map must include:

project mode and why it was selected;

key source materials;

entrypoints or primary deliverables;

relevant commands, if any;

source-of-truth data/docs;

dependencies and external systems;

generated or derived artifacts;

validation surfaces;

risk areas;

unknowns that require user or stakeholder input.

Write Scope

When used inside deep planning, write only to the target project's .deep-planning/repo-map.md and .deep-planning/evidence-catalog.md unless the user specifies another planning workfolder.