pathfinder
Разбор архитектуры и поиск дублирующей логики
Что получите
Папка PATHFINDER-<YYYY-MM-DD> в корне репозитория: описание функциональных областей, схемы Mermaid, отчёт о дублировании, предложение общей архитектуры и запросы для /make-plan.
Что передать
Репозиторий и описание систем, которые хочется разобрать или объединить.
Проверен состав файлов. Запуск не тестировался. Что проверено
Оценки пользователей
Как использовать
Помогает разработчикам разобраться в устройстве кодовой базы перед рефакторингом. Показывает, где системы повторяют друг друга и как их можно объединить без потери нужных различий.
- Определите функциональные области проекта и уточните их границы перед подробным разбором.
- Попросите построить схемы текущих потоков и найти существенные повторы внутри областей и между ними.
- Сравните предложение по объединению с текущим поведением, особенно возможную потерю возможностей.
Условия работы
- Для изучения исходников используются вспомогательные агенты; итоговые архитектурные решения принимает основной агент.
- Выводы должны опираться на конкретные места в исходниках. Обоснованную специализацию нельзя считать ненужным дублированием.
- Скилл заканчивает работу на предложении и передаче планирования; код реализации не пишет.
Пример запроса после установки
Разбери архитектуру нашего проекта перед рефакторингом: покажи повторяющуюся логику очередей и хранения, предложи объединение и подготовь запросы для /make-plan.
Пример составлен по инструкции автора; результат запуска не проверялся.
Основание: инструкция закреплённой версииДля установки
Node.js, npm и Git для команды выше. Подключения и инструменты для работы скилла настраиваются отдельно.
Совместимые агенты
Совместимость указана для инструкций. Запуск в каждом приложении не тестировался; для веб-чата способ подключения может отличаться.
Файлы скилла
GitHubЧитать инструкцию SKILL.md
Исходный текст закреплённой версии.
--- name: pathfinder description: Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts. --- # Pathfinder You are an ORCHESTRATOR. Map the codebase into feature-grouped flowcharts, identify duplicated concerns, propose the simplest unified architecture, and hand off per-system plans to `/make-plan`. You do not write implementation code. You produce diagrams, a duplication report, a proposed unified flowchart, and handoff prompts. ## Delegation Model Use subagents for *discovery and extraction* (file reading, flow tracing, grep, diagramming). Keep *synthesis* (deciding feature boundaries, picking unification strategies, final flowchart) with the orchestrator. Reject subagent reports that lack source citations and redeploy. ### Subagent Reporting Contract (MANDATORY) Each subagent response must include: 1. Sources consulted — exact file paths and line ranges read 2. Concrete findings — exact function names, call sites, data flow 3. Mermaid diagram(s) with nodes labeled by `file:line` 4. Confidence note + known gaps ## Output Artifacts All artifacts go in `PATHFINDER-<YYYY-MM-DD>/` at repo root: - `00-features.md` — feature inventory with boundaries - `01-flowcharts/<feature>.md` — one Mermaid flowchart per feature - `02-duplication-report.md` — cross-cutting duplicated concerns with evidence - `03-unified-proposal.md` — proposed unified architecture + Mermaid - `04-handoff-prompts.md` — copy-pasteable `/make-plan` prompts per unified system ## Phases ### Phase 0: Feature Discovery (ALWAYS FIRST) Deploy ONE "Feature Discovery" subagent to: 1. Walk the source tree (not built artifacts) and read top-level README / CLAUDE.md 2. Propose feature boundaries based on directory structure, import graph, and naming 3. Return a flat list of features with: name, entry points (file:line), core files, brief purpose Orchestrator reviews the proposal, adjusts boundaries if needed, writes `00-features.md`. Do NOT fan out until feature boundaries are approved. ### Phase 1: Per-Feature Flowcharts (FAN OUT) Deploy ONE "Flowchart" subagent per feature in parallel. Each receives only its feature's scope. Each must: 1. Trace the feature's primary happy path from entry point to terminal state 2. Identify side effects (DB writes, HTTP calls, file I/O, process spawns) 3. Note error and fallback branches but do not let them dominate the diagram 4. Produce a Mermaid `flowchart TD` with every node labeled `Name<br/>file:line` 5. List external dependencies (other features it calls into) at the bottom Orchestrator writes each flowchart to `01-flowcharts/<feature>.md`. Reject any diagram missing `file:line` labels. ### Phase 2: Duplication Hunt Deploy TWO subagents in parallel: **"Within-Feature Duplication"** subagent: - For each feature, find repeated code/logic patterns inside the feature only - Report only duplications worth consolidating (ignore trivial repetition) **"Cross-Feature Duplication"** subagent: - Compare flowcharts across features for concerns that appear in multiple places - Examples of what to look for: multiple capture paths, parallel queue implementations, duplicated storage/migration code, repeated agent scaffolding, parallel parsing layers - For each duplication, report: (a) the concern, (b) every location with `file:line`, (c) why they diverged, (d) whether the divergence is legitimate specialization or accidental Orchestrator synthesizes both into `02-duplication-report.md`. Every duplication claim must cite ≥2 `file:line` locations. ### Phase 3: Unified Proposal (ORCHESTRATOR) The orchestrator writes `03-unified-proposal.md` itself — do not delegate synthesis. For each duplicated concern from Phase 2 that is NOT legitimate specialization: 1. Propose the simplest unified design (one path, one store, one handler — whatever applies) 2. Name the consolidated component and its single entry point 3. Show what each old call site becomes 4. Call out any loss of capability and whether it's acceptable End the document with ONE combined Mermaid flowchart showing the proposed unified system. Nodes still labeled with target `file:line` (new or existing) where knowable. **Anti-patterns to reject in your own proposal:** - Adding a new abstraction layer "for flexibility" - Keeping both old paths behind a feature flag - Introducing a registry/factory when a switch statement suffices - Preserving divergent behavior "just in case" ### Phase 4: Per-System Handoff Prompts For each unified system in the proposal, write a ready-to-run `/make-plan` prompt to `04-handoff-prompts.md`. Each prompt must: 1. State the target unified component and its single entry point 2. List the exact call sites to rewrite (from Phase 2 evidence) 3. Cite the relevant flowchart file from `01-flowcharts/` 4. Include anti-pattern guards specific to this system Format each as a fenced code block the user can copy directly into `/make-plan`. ## Key Principles - **Evidence over intuition** — every diagram node and duplication claim cites `file:line` - **Current state before ideal state** — Phases 0–2 describe what IS; Phase 3 describes what SHOULD BE - **Simplest unification wins** — prefer deletion over abstraction; prefer one path over configurable paths - **Specialization is not duplication** — two components serving different trust models or data sources are legitimate even if their code looks similar - **Handoff, don't implement** — Pathfinder ends at plan prompts; `/make-plan` and `/do` take it from there ## Failure Modes to Prevent - Drawing flowcharts from memory instead of source — redeploy subagent with grep evidence requirement - Proposing unification of legitimately specialized components — re-examine trust/data-source divergence - Handoff prompts that lack concrete call sites — rewrite with Phase 2 evidence - Skipping Phase 0 boundary review — fanning out on bad feature boundaries wastes all of Phase 1
Проверка и особенности
Автоматическая проверка источника и файлов
Автоматически сверены публичный репозиторий, лицензия, YAML-заголовок SKILL.md, состав папки и Git-хеш каждого файла. Исполняемые файлы и срабатывания статических правил исключены из этой партии. Ручной аудит всех инструкций и проверка работы не проводились; эта проверка не гарантирует безопасность. Команда закреплена на проверенном коммите.
Интерес к репозиторию оцениваем по звёздам и форкам GitHub. Это показатели всего репозитория, а не числа установок отдельного скилла.
- Проверка состава
- 16.09.2026
- Проверенная версия
d8bc9755e749- Файлы с кодом
- Не указаны в данных проверки
- Изменения на GitHub
- Нужна повторная проверкаПоследняя проверка: 11.10.2026
Репозиторий и лицензия
Это показатели всего репозитория, а не установки скилла. Снимок требует обновления.
- Последняя активность GitHub
- 09.10.2026
- Лицензия
- Apache-2.0
- Добавлен в каталог
- 16.09.2026
Полный текст лицензии
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Ещё в этой категории
Все в категорииОбсуждение
ПравилаПользовались этим скиллом? Делитесь опытом без регистрации. Все комментарии проверяет модератор.
