You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .devcontainer/CHANGELOG.md
+69Lines changed: 69 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,74 @@
1
1
# CodeForge Devcontainer Changelog
2
2
3
+
## [v1.11.0] - 2026-02-17
4
+
5
+
### Added
6
+
7
+
#### New Feature: ccms (Session History Search)
8
+
-**`ccms` devcontainer feature** — Rust-based CLI for searching Claude Code session JSONL files. Installed via `cargo install`. Supports boolean queries, role filtering, time scoping, project isolation, and JSON output
9
+
-**`session-search.md` rule** — global rule requiring project-scoped `ccms` usage and documenting CLI flags/query syntax
10
+
-**Rust runtime** — added `ghcr.io/devcontainers/features/rust:1` as a devcontainer feature (required by ccms)
11
+
-**System prompt `<session_search>` section** — inline reference for ccms usage with key flags and examples
12
+
-**Context management updated** — `<context_management>` now references ccms as the primary recovery tool for compacted sessions (three-source recovery: session history → source files → plan/requirement files)
13
+
14
+
#### New Feature: ccw (Writing Mode)
15
+
-**`ccw` alias** — launches Claude with `writing-system-prompt.md` for creative-writing tasks
16
+
-**`writing-system-prompt.md`** — dedicated system prompt for writing mode, distributed via file-manifest
17
+
18
+
#### New Plugin: workspace-scope-guard
19
+
-**`workspace-scope-guard`** — safety plugin that blocks writes and warns on reads outside the working directory. Registered in marketplace.json and enabled by default in settings.json
-**`/spec-build`** — orchestrates the full implementation lifecycle from an approved spec: plan, build, review, and close in one pass. 5-phase workflow with acceptance criteria markers (`[ ]` → `[~]` → `[x]`)
23
+
-**`/spec-review`** — standalone deep implementation review against a spec. Reads code, verifies requirements and acceptance criteria, recommends `/spec-update` when done
24
+
25
+
#### New Hook: inject-cwd.py
26
+
-**`inject-cwd.py`** (PostToolUse, all tools) — injects current working directory into every tool response via `additionalContext`
27
+
28
+
#### Status Line: CWD Widget
29
+
-**`ccstatusline-cwd`** — new custom-command widget showing the basename of Claude Code's working directory. Layout expanded from 7 to 8 lines (16 → 17 widgets)
30
+
31
+
### Changed
32
+
33
+
#### setup-aliases.sh Idempotency Fix
34
+
-**Block-marker strategy** — replaced cleanup+guard approach (which left aliases missing on re-run) with a delete-and-rewrite strategy using `START`/`END` block markers. The managed block is removed wholesale by sed range match, then always re-written fresh — no guard/`continue` needed
35
+
-**Legacy cleanup expanded** — added removal of v1.10.0 orphaned aliases/exports/`_CLAUDE_BIN`/`cc-tools()` that existed outside block markers, in addition to pre-v1.10.0 function forms
36
+
-**cc-tools expanded** — added `ccw`, `ccms`, `cargo` to the tool listing
-**Directory structure** — specs now live in domain subfolders (`.specs/{domain}/{feature}.md`) instead of version directories (`.specs/v0.1.0/feature.md`)
40
+
-**ROADMAP.md → MILESTONES.md** — version tracker renamed to milestone tracker throughout all skills, templates, and system prompt
41
+
-**`**Version:**` → `**Domain:**`** — spec template metadata field renamed across spec-new template, spec-writer agent, specification-writing skill, spec-update, spec-check
-**Acceptance criteria markers** — three-state progress tracking: `[ ]` (not started), `[~]` (implemented, not yet verified), `[x]` (verified). Used by `/spec-build` phases and recognized by `/spec-check` and `/spec-update`
44
+
-**Spec lifecycle expanded** — `/spec-review` inserted before `/spec-update` in the recommended post-implementation workflow. `spec-reminder.py` advisory message updated accordingly
Copy file name to clipboardExpand all lines: .devcontainer/CLAUDE.md
+15-6Lines changed: 15 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,16 @@ CodeForge devcontainer for AI-assisted development with Claude Code.
14
14
│ │ └── defaults/ # Files copied per manifest
15
15
│ │ ├── settings.json # Claude Code settings
16
16
│ │ ├── keybindings.json # Claude Code keybindings
17
-
│ │ └── main-system-prompt.md
17
+
│ │ ├── main-system-prompt.md
18
+
│ │ └── writing-system-prompt.md
18
19
│ ├── features/ # Custom devcontainer features
19
20
│ ├── plugins/ # Local plugin marketplace
20
21
│ │ └── devs-marketplace/
21
22
│ └── scripts/ # Setup scripts
22
23
├── .claude/ # Runtime Claude config (created on first run)
23
24
│ ├── settings.json # Active settings (managed by file-manifest.json)
24
25
│ ├── keybindings.json # Active keybindings
25
-
│ └── system-prompt.md # Active system prompt
26
+
│ └── main-system-prompt.md # Active system prompt
26
27
└── .gh/ # GitHub CLI config (persists across rebuilds)
27
28
└── hosts.yml # Authenticated hosts
28
29
```
@@ -37,6 +38,7 @@ CodeForge devcontainer for AI-assisted development with Claude Code.
37
38
|`config/defaults/settings.json`| Claude Code defaults: model, tokens, permissions, plugins |
38
39
|`config/defaults/keybindings.json`| Claude Code keybindings (empty by default — customizable) |
39
40
|`config/defaults/main-system-prompt.md`| Default system prompt defining assistant behavior |
41
+
|`config/defaults/writing-system-prompt.md`| Creative-writing system prompt used by `ccw` alias |
40
42
41
43
> **Note**: Config file copying is controlled by `config/file-manifest.json`. Each entry specifies `overwrite`: `"if-changed"` (default, sha256-based), `"always"`, or `"never"`. Persistent changes go in `.devcontainer/config/defaults/settings.json`.
42
44
@@ -47,12 +49,14 @@ CodeForge devcontainer for AI-assisted development with Claude Code.
47
49
|`claude`| Run Claude Code with auto-configuration (prefers native binary at `~/.local/bin/claude`) |
48
50
|`cc`| Shorthand for `claude` with config |
49
51
|`ccraw`| Vanilla Claude Code without any config (bypasses function override) |
52
+
|`ccw`| Shorthand for `claude` with writing system prompt |
**External features with `version: "none"` support:**
109
113
`ghcr.io/devcontainers/features/node`, `ghcr.io/devcontainers/features/github-cli`, `ghcr.io/devcontainers/features/docker-outside-of-docker`, `ghcr.io/devcontainers/features/go` (all official Microsoft features)
110
114
111
115
**External features without `version: "none"` support:**
**External features with `version: "none"` support (Rust):**
119
+
`ghcr.io/devcontainers/features/rust` (official Microsoft feature)
120
+
114
121
> **Convention**: Every new local feature must include a `version` option (default `"latest"`) in its `devcontainer-feature.json` and a skip guard at the top of `install.sh`:
115
122
> ```bash
116
123
>if [ "${VERSION}"="none" ];then
@@ -127,7 +134,7 @@ Scripts in `./scripts/` run via `postStartCommand`:
127
134
|--------|---------|
128
135
|`setup.sh`| Main orchestrator |
129
136
|`setup-config.sh`| Copies config files per `config/file-manifest.json` to destinations |
130
-
|`setup-aliases.sh`| Creates `cc`/`claude`/`ccraw` shell aliases (prefers native binary at `~/.local/bin/claude` via `_CLAUDE_BIN`) |
137
+
|`setup-aliases.sh`| Creates `cc`/`claude`/`ccraw`/`ccw` shell aliases (prefers native binary at `~/.local/bin/claude` via `_CLAUDE_BIN`) |
131
138
|`setup-plugins.sh`| Registers local marketplace + installs official Anthropic plugins |
132
139
|`setup-update-claude.sh`| Installs native Claude Code binary on first run; background auto-updates on subsequent starts |
133
140
|`setup-terminal.sh`| Configures VS Code Shift+Enter keybinding for Claude Code multi-line input |
@@ -157,6 +164,7 @@ Plugins are declared in `config/defaults/settings.json` under `enabledPlugins` a
157
164
-`auto-formatter@devs-marketplace` — Batch-formats edited files at Stop (Ruff for Python, Biome for JS/TS/CSS/JSON/GraphQL/HTML; also supports shfmt, dprint, gofmt, rustfmt when installed)
158
165
-`auto-linter@devs-marketplace` — Auto-lints edited files at Stop (Pyright + Ruff for Python, Biome for JS/TS/CSS/GraphQL; also supports ShellCheck, hadolint, go vet, clippy when installed)
Copy file name to clipboardExpand all lines: .devcontainer/README.md
+22-11Lines changed: 22 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -243,7 +243,7 @@ For conflicting shortcuts, use Meta (Alt) variants or add custom keybindings.
243
243
244
244
### System Prompt
245
245
246
-
The default system prompt is in `.devcontainer/config/defaults/main-system-prompt.md`. Override it by creating a `.claude/system-prompt.md` in your project directory.
246
+
The default system prompt is in `.devcontainer/config/defaults/main-system-prompt.md`. Override it by creating a `.claude/main-system-prompt.md` in your project directory.
247
247
248
248
## Custom Features
249
249
@@ -265,6 +265,14 @@ CodeForge includes several custom devcontainer features:
265
265
|`mcp-qdrant`| Qdrant vector database MCP server (optional) |
266
266
|`mcp-reasoner`| Enhanced AI reasoning MCP server (optional) |
|`protected-files-guard`| Blocks modifications to .env, lock files, .git/, and credentials |
274
+
|`workspace-scope-guard`| Enforces working directory scope — blocks writes and warns on reads outside the project |
275
+
268
276
## Agents & Skills
269
277
270
278
The `code-directive` plugin includes specialized agent definitions and coding reference skills.
@@ -307,7 +315,7 @@ CodeForge includes a specification-driven development workflow. Every non-trivia
307
315
308
316
```bash
309
317
/spec-init # Bootstrap .specs/ directory (first time only)
310
-
/spec-new auth-flow v0.2.0# Create a feature spec
318
+
/spec-new auth-flow # Create a feature spec (domain is inferred)
311
319
/spec-refine auth-flow # Validate assumptions with user
312
320
# ... implement the feature ...
313
321
/spec-update auth-flow # As-built update after implementation
@@ -317,7 +325,7 @@ CodeForge includes a specification-driven development workflow. Every non-trivia
317
325
### The Lifecycle
318
326
319
327
1.**Backlog** — features live in `.specs/BACKLOG.md` with priority grades (P0–P3)
320
-
2.**Roadmap** — when starting a version, pull features from backlog into `.specs/ROADMAP.md`
328
+
2.**Milestone** — when starting a milestone, pull features from backlog into `.specs/MILESTONES.md`
321
329
3.**Spec** — `/spec-new` creates a spec from the standard template with all requirements tagged `[assumed]`
322
330
4.**Refine** — `/spec-refine` walks through every assumption with the user, converting `[assumed]` → `[user-approved]`. The spec's approval status moves from `draft` → `user-approved`. **No implementation begins until approved.**
323
331
5.**Implement** — build the feature using the spec's acceptance criteria as the definition of done
@@ -337,26 +345,29 @@ A spec-reminder advisory hook fires at Stop when code was modified but specs wer
337
345
338
346
| Skill | Purpose |
339
347
|-------|---------|
340
-
|`/spec-init`| Bootstrap `.specs/` directory with ROADMAP and BACKLOG |
348
+
|`/spec-init`| Bootstrap `.specs/` directory with MILESTONES and BACKLOG |
341
349
|`/spec-new`| Create a feature spec from the standard template |
342
350
|`/spec-refine`| Validate assumptions and get user approval (required before implementation) |
343
351
|`/spec-update`| As-built update after implementation |
344
352
|`/spec-check`| Audit all specs for health issues |
353
+
|`/spec-build`| Orchestrate full implementation from an approved spec (plan, build, review, close) |
354
+
|`/spec-review`| Standalone deep implementation review against a spec |
345
355
|`/specification-writing`| EARS format templates and acceptance criteria patterns |
346
356
347
357
### Directory Structure
348
358
349
359
```
350
360
.specs/
351
-
├── ROADMAP.md # Current version scope
352
-
├── BACKLOG.md # Priority-graded feature backlog
353
-
├── v0.1.0.md # Single-file spec (small versions)
354
-
└── v0.2.0/ # Multi-feature version
355
-
├── _overview.md # Parent linking sub-specs
356
-
└── feature.md # Individual feature spec
361
+
├── MILESTONES.md # Milestone tracker linking to feature specs
362
+
├── BACKLOG.md # Priority-graded feature backlog
363
+
├── auth/ # Domain folder
364
+
│ ├── login-flow.md # Feature spec
365
+
│ └── oauth.md # Feature spec
366
+
└── search/ # Domain folder
367
+
└── full-text.md # Feature spec
357
368
```
358
369
359
-
Specs aim for ~200 lines each. Split by feature boundary when longer; link via a parent overview.
370
+
All specs live in domain subfolders. Specs aim for ~200 lines each; split into separate specs in the domain folder when longer.
0 commit comments