@pourkit/cli 0.0.0-next-20260707210730 → 0.0.0-next-20260709181702
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js
CHANGED
|
@@ -13487,6 +13487,10 @@ function buildManagedAgentInstructions(options) {
|
|
|
13487
13487
|
|
|
13488
13488
|
Use \`fd\` for file discovery, \`rg\` for text search, and direct file reads for focused context.
|
|
13489
13489
|
|
|
13490
|
+
Use the \`explore-codebase\` skill when the user asks to explore or map a codebase, including an external package or repository, find feature/module ownership, identify entry points/tests/docs, or produce a Codebase Navigation Atlas.
|
|
13491
|
+
|
|
13492
|
+
Also check the \`explore-codebase\` skill for research-oriented codebase queries, such as requests to research, investigate, crawl, survey, or understand a domain before changing code.
|
|
13493
|
+
|
|
13490
13494
|
For multi-step exploration, prefer the dedicated subagents in \`.opencode/agents\`:
|
|
13491
13495
|
|
|
13492
13496
|
- Use \`codebase-locator\` when you need to find relevant files, directories, or entry points.
|
|
@@ -13497,7 +13501,7 @@ For multi-step exploration, prefer the dedicated subagents in \`.opencode/agents
|
|
|
13497
13501
|
|
|
13498
13502
|
Use direct \`fd\`/\`rg\`/reads for focused checks; use subagents when the search would otherwise require several discovery/read steps.
|
|
13499
13503
|
|
|
13500
|
-
Use \`opensrc path <package-or-repo>\` whenever implementation requires reading external source code, not only package dependencies. If you would otherwise clone a repository to inspect its source, use \`opensrc\` first, then search or read files under the returned source path with \`rg\` and direct file reads.
|
|
13504
|
+
Use the \`explore-codebase\` skill as the main route for broad external-source exploration. Inside that workflow, use \`opensrc path <package-or-repo>\` whenever implementation requires reading external source code, not only package dependencies. For focused external-source checks, use \`opensrc\` directly. If you would otherwise clone a repository to inspect its source, use \`opensrc\` first, then search or read files under the returned source path with \`rg\` and direct file reads.
|
|
13501
13505
|
|
|
13502
13506
|
Follow the project's domain docs and workflow routes documented in the Pourkit managed block below.
|
|
13503
13507
|
|
|
@@ -19360,11 +19364,11 @@ function createCliProgram(version) {
|
|
|
19360
19364
|
return program;
|
|
19361
19365
|
}
|
|
19362
19366
|
async function resolveCliVersion() {
|
|
19363
|
-
if (isPackageVersion("0.0.0-next-
|
|
19364
|
-
return "0.0.0-next-
|
|
19367
|
+
if (isPackageVersion("0.0.0-next-20260709181702")) {
|
|
19368
|
+
return "0.0.0-next-20260709181702";
|
|
19365
19369
|
}
|
|
19366
|
-
if (isReleaseVersion("0.0.0-next-
|
|
19367
|
-
return "0.0.0-next-
|
|
19370
|
+
if (isReleaseVersion("0.0.0-next-20260709181702")) {
|
|
19371
|
+
return "0.0.0-next-20260709181702";
|
|
19368
19372
|
}
|
|
19369
19373
|
try {
|
|
19370
19374
|
const root = repoRoot();
|