dsh-gpt-file-discipline

Readme

# dsh-gpt-file-discipline

`dsh-gpt-file-discipline` is a small DeepSeek Harness host plugin that silently switches one conditional system-prompt section by model route. It waits for downstream waterfall listeners before matching, so it uses the provider and model chosen for the exact step rather than an earlier route candidate.

- **GPT route** (`provider` is exactly `codex` and the model starts with `gpt-`): appends the file-discipline section.
- **DeepSeek route** (the provider or the model starts with `deepseek`): appends the DeepSeek thought-language section.
- **Any other route**: returns the downstream assembly completely unchanged.

The plugin registers no static prompt section. The only prompt content it can add is the one appended section after a route matches, so an unmatched route costs no extra context, token, filtering, or section overhead.

## Install for a DSH profile

After this repository is published, add it to a DSH profile with the GitHub package spec:

```sh
dsh plugin --profile <profile> add github:youxi-huang/dsh-gpt-file-discipline
```

The package declares `cordis.patch.yml` as its bundle patch. Its official patch-entry array mounts one plugin row:

```yml
- insert:
    - id: gpt-file-discipline
      name: dsh-gpt-file-discipline
```

Cordis validates the exported Schemastery `Config`, applies its defaults, and owns listener registration and cleanup.

## Defaults

| Route | Match | Section | Text |
| --- | --- | --- | --- |
| GPT | provider `codex` + model prefix `gpt-` (case-insensitive) | `model-file-discipline` | File-discipline guidance (below) |
| DeepSeek | provider or model prefix `deepseek` (case-insensitive) | `route:deepseek-thought` | Thought-language guidance (below) |

GPT text:

> Local documents span many loosely related systems and include dormant or retired material, so do not browse files speculatively: locate the relevant source first, read only the smallest necessary passages, and stay strictly within the user-defined scope.

DeepSeek text:

> **when you thought,thought in ENGLISH,start with "We need..."**

> Attribution note: the DeepSeek line is community-shared text from a Bilibili comment section, not original work by this package's author. Its effectiveness is anecdotal; keep it only if it proves useful.

If the matching route's section already exists, the plugin leaves the assembly unchanged. DeepSeek is checked before GPT.

## Configuration

Cordis configuration patches are top-level patch-entry arrays. A configured insert for both routes looks like this:

```yml
- insert:
    - id: gpt-file-discipline
      name: dsh-gpt-file-discipline
      config:
        provider: codex
        modelPrefix: gpt-
        gptText: Use only the designated project sources.
        sectionName: route:gpt-file-discipline
        deepseekProviderPrefix: deepseek
        deepseekModelPrefix: deepseek
        deepseekText: '**when you thought,thought in ENGLISH,start with "We need..."**'
        deepseekSectionName: route:deepseek-thought
        caseSensitive: false
```

| Field | Default | Meaning |
| --- | --- | --- |
| `provider` | `codex` | Exact provider required for the GPT route. |
| `modelPrefix` | `gpt-` | Model prefix required for the GPT route. |
| `promptText` | file-discipline text | GPT text, kept from the original plugin API. |
| `gptText` | _unset_ | Optional alias that overrides `promptText` when supplied. |
| `sectionName` | `model-file-discipline` | Section name appended for the GPT route. |
| `deepseekProviderPrefix` | `deepseek` | Prefix for provider-based DeepSeek matching. |
| `deepseekModelPrefix` | `deepseek` | Prefix for model-based DeepSeek matching. |
| `deepseekText` | DeepSeek text above | Section text appended for the DeepSeek route. |
| `deepseekSectionName` | `route:deepseek-thought` | Section name appended for the DeepSeek route. |
| `caseSensitive` | `false` | Enables case-sensitive prefix matching. |

Text fields must be nonblank strings. Section names must be 1–128 characters, start with a letter or digit, and contain only letters, digits, `.`, `_`, `:`, or `-`. `caseSensitive` must be a boolean.

Profile installation applies the bundle to the DSH host, so the inserted plugin is host-wide. For preset-only use, make the package resolvable to DSH without adding its bundle layer, then add an ordinary plugin row to that preset's top-level entry list:

```yml
- id: gpt-file-discipline
  name: dsh-gpt-file-discipline
  config:
    provider: codex
    modelPrefix: gpt-
    sectionName: route:gpt-file-discipline
```

One practical route is to install the package as a dependency and then remove `dsh-gpt-file-discipline` from that profile's `dsh.profile.bundles` list before mounting the row in the preset. Do not use a map keyed by package name: agent preset compositions are top-level arrays of plugin rows.

## Uninstall

Remove it from the same DSH profile using the installed package name:

```sh
dsh plugin --profile <profile> remove dsh-gpt-file-discipline
```

This removes the bundle-managed Cordis row; unloading the plugin disposes its listener registration.

## Development

The committed `index.js` is the package entry point; no build or prepare step is required.

```sh
npm run check:syntax
npm test
```

## License

MIT © 2026 youxi-huang