Sup coding
A Rust-based Telegram AI assistant powered by OpenRouter LLM with built-in sandboxed tools, scheduling, persistent memory, and MCP server integration.
npx -y skills add chinkan/RustFox --skill sup-codingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish)
SKILL.md
0.8 KB, as published. Nobody here has run it
When to use
When a task is classified as code_change, bug_fix, or refactor.
Operating rules
- Always run inside an isolated branch/worktree.
- Always run formatter, linter, and tests before declaring success.
- Verification evidence: at minimum one passing test or one confirmed diff.
- Prefer test-driven development: write a failing test, then make it pass.
- Keep commits small and logically scoped.
Stop conditions
- All planned changes implemented.
- Verification passes (build, tests, lint, format).
- Reviewer notes are addressed.