qwen-forge
Skill0 starsChanged 46 days agoMITView on GitHub
Local-Qwen lifecycle conductor (token-free; requires a local OpenAI-compatible model endpoint such as vLLM, SGLang, llama.cpp or Ollama). Detects the project's stage with simple file checks and runs the matching qwen-* skill (qwen-kickstart → qwen-project-autopilot → qwen-ship-it) sequentially on one GPU. The mechanical, checklist form of /forge for a small local model. Use when you want /forge's job done on a local model with no API tokens, running the full build lifecycle at zero token cost.
In this repository51 other files it gives its agents.
- advisor-councilSkill
- advisor-persona-buildSkill
- agent-exploit-pathsSkill
- agentic-loopsSkill
- ai-receptionist-tenant-onboardingSkill
- audit-lensSkill
- beadsmithSkill
- bug-sweepSkill
- bug-zeroSkill
- build-in-public-scope-guardSkill
- consulting-sales-playbookSkill
- deepenSkill
- deposit-first-shippingSkill
- design-intelSkill
- dueling-idea-forgeSkill
- forgeSkill
- hotspot-scoutSkill
- idea-forgeSkill
- incident-zeroSkill
- kickstartSkill
- local-llm-opsSkill
- memguardSkill
- memory-forgeSkill
- migrate-proofSkill
- no-slop-bug-hunterSkill
- optimize-proofSkill
- perf-maxSkill
- polish-passSkill
- problem-breakthroughSkill
- project-autopilotSkill
- qwen-bug-zeroSkill
- qwen-kickstartSkill
- qwen-perf-maxSkill
- qwen-project-autopilotSkill
- qwen-ship-itSkill
- qwen-ux-maximizerSkill
- readme-realSkill
- reality-checkSkill
- recallSkill
- security-sweepSkill
- session-mineSkill
- ship-itSkill
- simplify-proofSkill
- skillifySkill
- stream-demo-prepSkill
- swarm-runSkill
- test-maxSkill
- trace-itSkill
- unslopSkill
- ux-maximizerSkill
- ux-scanSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Read README.md + AGENTS.md fully.
- Distinctive: line 50
Make sure it builds + tests pass right now (baseline).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
qwen-forge (local conductor)
The Qwen-run version of /forge. Same arc, mechanical form: detect the stage by concrete checks (not judgment), run the matching qwen-* skill, advance. One GPU, so sequential.
QWEN LOCAL RULES (obey every step; full text: references/QWEN-MODE.md)
- You are a builder, not an architect. Judgment calls belong to the user.
- ONE small change at a time. After each: build → tests → lint. Green → commit + report. Red → revert, one retry, else STOP and ask. Never weaken tests.
- Build ONLY what the Intent needs; extra ideas → SOMEDAY.md.
- Unclear / judgment call / outward-or-irreversible → write to .autopilot/DECISIONS.md and STOP.
- Local endpoint required: a local OpenAI-compatible endpoint (vLLM, SGLang, llama.cpp or Ollama) serving a capable Qwen-class coding model. ONE model loaded, work SEQUENTIALLY, leave memory headroom on unified-memory machines.
Detect the stage (simple checks, in order)
1. Empty repo / no source / no build file (no package.json, Cargo.toml, etc.)
→ run qwen-kickstart (0→1: scaffold it)
2. It builds and has tests, but features are incomplete vs the Intent
→ run qwen-project-autopilot (1→done)
3. It builds, tests pass, and it delivers the Intent
→ run qwen-ship-it (pre-flight only; buttons belong to the user)
4. Already shipped → STOP, report.Loop
a. Detect the stage (above).
b. Run that one qwen-* skill; let it finish its own loop.
c. When it reports done, re-detect and go to the next stage.
d. STOP for the user at: any ship button, any DECISIONS.md item, or anything you're unsure about.First steps
- Read README.md + AGENTS.md fully; say back in 3 bullets what the project is.
- Make sure it builds + tests pass right now (baseline). If not and a scaffold exists, that's qwen-project-autopilot's first job: fix the baseline before new work.
- Detect the stage and begin.
Notes
- This is the zero-token local option. For higher quality at near-zero spend, run HYBRID (a short Claude session plans/reviews; Qwen executes). See references/QWEN-MODE.md.
- Distilled from /forge. That skill (and project-autopilot's references) hold the full judgment-rich version if a human or Claude is driving instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

