mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-23 03:27:50 +09:00
fix(qwen): integrate native workflow context and quote remaining hint
This commit is contained in:
2 files changed
+67
-17
No files matched your search
+66
-16
@@ -1,25 +1,75 @@
|
||||
# Qwen CLI Configuration
|
||||
# ECC for Qwen Code
|
||||
|
||||
This directory contains ECC's Qwen CLI install template.
|
||||
This file provides Qwen Code with the baseline ECC workflow, review standards, and security checks for installations that use the `qwen` target.
|
||||
|
||||
## Runtime Location
|
||||
## Overview
|
||||
|
||||
The source `.qwen/` directory in this repository is copied into a user's home-level `~/.qwen/` install root when running:
|
||||
ECC is a cross-harness coding system with specialized agents, skills, and commands.
|
||||
|
||||
```bash
|
||||
./install.sh --target qwen --profile minimal
|
||||
```
|
||||
The Qwen target installs the full managed manifest surface into `~/.qwen/`: `rules/`, `agents/`, `commands/`, `skills/`, and `mcp-configs/`. This file carries Qwen-specific guidance; repo-wide operating rules live in `AGENTS.md`. Qwen Code 0.25.0 loads both at the home level under default settings, but `AGENTS.md` is not the documented default context filename, so set `context.fileName` if a later release stops loading it.
|
||||
|
||||
The managed install also writes `~/.qwen/ecc-install-state.json` so future ECC updates and uninstalls can distinguish ECC-owned files from user-owned Qwen configuration.
|
||||
`docs/QWEN-GUIDE.md` covers install layout, updating, and uninstalling. It lives in the ECC repository and is **not** copied into `~/.qwen/`, so read it from a checkout or from <https://github.com/affaan-m/ecc/blob/main/docs/QWEN-GUIDE.md>.
|
||||
|
||||
## Installed Surface
|
||||
## Core Workflow
|
||||
|
||||
The Qwen target installs the same managed manifest modules used by other harness adapters:
|
||||
1. Plan before editing large features.
|
||||
2. Prefer test-first changes for bug fixes and new functionality.
|
||||
3. Review for security before shipping.
|
||||
4. Keep changes self-contained, readable, and easy to revert.
|
||||
|
||||
- `rules/`
|
||||
- `agents/`
|
||||
- `commands/`
|
||||
- `skills/`
|
||||
- `mcp-configs/`
|
||||
## Coding Standards
|
||||
|
||||
Hook runtime files are intentionally not selected for Qwen until the Qwen hook/event contract is verified.
|
||||
- Prefer immutable updates over in-place mutation.
|
||||
- Keep functions small and files focused.
|
||||
- Validate user input at boundaries.
|
||||
- Never hardcode secrets.
|
||||
- Fail loudly with clear error messages instead of silently swallowing problems.
|
||||
|
||||
## Security Checklist
|
||||
|
||||
Before any commit:
|
||||
|
||||
- No hardcoded API keys, passwords, or tokens
|
||||
- All external input validated
|
||||
- Parameterized queries for database writes
|
||||
- Sanitized HTML output where applicable
|
||||
- Authz/authn checked for sensitive paths
|
||||
- Error messages scrubbed of sensitive internals
|
||||
|
||||
## Delivery Standards
|
||||
|
||||
- Use conventional commits: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf`, `ci`
|
||||
- Run targeted verification for touched areas before shipping
|
||||
- Prefer contained local implementations over adding new third-party runtime dependencies
|
||||
|
||||
## Reading ECC Content On Qwen Code
|
||||
|
||||
ECC skills, rules, and agent prompts are authored against Claude Code tool names. Qwen Code uses different identifiers, so translate them when following instructions:
|
||||
|
||||
| In ECC content | Qwen Code tool |
|
||||
| --- | --- |
|
||||
| `Read` | `read_file` |
|
||||
| `Write` | `write_file` |
|
||||
| `Edit`, `MultiEdit` | `edit` |
|
||||
| `Bash` | `run_shell_command` |
|
||||
| `Grep` | `grep_search` |
|
||||
| `Glob` | `glob` |
|
||||
| `WebFetch` | `web_fetch` |
|
||||
| `TodoWrite` | `todo_write` |
|
||||
| `Task` | `agent` |
|
||||
| `WebSearch` | `web_search` where the provider supports it; otherwise `web_fetch` against a known URL |
|
||||
|
||||
Invoke a skill with the `skill` tool using the plain kebab-case name exactly as the session catalog lists it. Dispatch a subagent with the `agent` tool; top-level subagents run in the background and report through a completion notification rather than returning inline.
|
||||
|
||||
Some Qwen Code tools are deferred until their schema is reviewed — reach them with `tool_search`, then invoke them with `tool_call`. `web_fetch`, `web_search`, `send_message`, `task_stop`, and `record_artifact` are deferred by default, so a skill that names one of those is still actionable.
|
||||
|
||||
## Not Available On This Target
|
||||
|
||||
Hook runtime files are intentionally not selected for Qwen until its hook/event contract is confirmed (see the Scope section of `docs/QWEN-GUIDE.md` in the ECC repository). Hook-driven ECC features therefore do not run here: do not report a hook-enforced guard, format-on-save pass, or cost-tracking metric as active. `mcp-configs/` ships connector baselines but is not merged into Qwen's own settings, so an MCP-backed skill needs its server registered before it can work.
|
||||
|
||||
## ECC Areas To Reuse
|
||||
|
||||
- `AGENTS.md` for repo-wide operating rules
|
||||
- `skills/` for deep workflow guidance
|
||||
- `commands/` for slash-command patterns worth adapting into prompts/macros
|
||||
- `mcp-configs/` for shared connector baselines
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
description: Render a token-usage stat card from local agent session logs and commit it to the repo. Invokes the token-card skill.
|
||||
argument-hint: [--out PATH] [--theme auto|light|dark] [--dry-run]
|
||||
argument-hint: "[--out PATH] [--theme auto|light|dark] [--dry-run]"
|
||||
---
|
||||
|
||||
# Token Card
|
||||
|
||||
Reference in new issue
Block a user