Updated 2w ago
by ilang-ai
autocode
You say it. AutoCode ships it. 48 skills. Code to deployment in one session. iLang v5.0 judgment + secret-safe deploys. Free forever.
107 GitHub stars (107)
+4 in 30 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | +1 |
| Sep 30 | −1 |
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
| Oct 17 | 0 |
| Oct 18 | +1 |
| Oct 19 | 0 |
| Oct 20 | 0 |
| Oct 21 | 0 |
| Oct 22 | 0 |
| Oct 23 | 0 |
| Oct 24 | 0 |
| Oct 25 | 0 |
| Oct 26 | 0 |
| Oct 27 | 0 |
| Oct 28 | +1 |
| Oct 29 | +1 |
| Oct 30 | 0 |
| Oct 31 | 0 |
| Nov 1 | 0 |
| Nov 2 | +1 |
| Nov 3 | 0 |
| Nov 4 | 0 |
| Nov 5 | 0 |
- 11 skills (11 skills found in its SKILL.md files)
- 22 forks (22 forks)
- 2w ago last update (Last updated 2w ago)
Install
Skills CLI
npx skills add ilang-ai/autocode
Asks which skills and agents to install. Just one: npx skills add ilang-ai/autocode --skill build — add -g for every project.
Claude Code
git clone https://github.com/ilang-ai/autocodecp -r "autocode/skills/build" ~/.claude/skills/
Copies the build skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add ilang-ai/autocode
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
build
S4 of see-it-ship-it: build one feature at a time, simplest stack that works, checkpoint before anything risky, rules kept apart from the look so they can be verified without a browser, learned numbers tagged. Includes first-session environment setup and running where you build.
skills/build/ on GitHub (opens in a new tab)SKILL.md -
fix
Cross-cutting: when something breaks. Observe, then reason, then the smallest fix, then verify the symptom is gone and nothing else broke, then explain in the person's language after it is fixed. Never show a raw error to a beginner; never blame them.
skills/fix/ on GitHub (opens in a new tab)SKILL.md -
hand-back
S7 of see-it-ship-it: what the person hears. Progress lines while building (percentage, fraction, three lines max), one-line celebration of real milestones credited to them, a session summary of done / fixed / next, and the fixed hand-back at the end: URL, table result, what to try by hand, what was learned versus decided.
skills/hand-back/ on GitHub (opens in a new tab)SKILL.md -
judge
The judgment layer: when AutoCode acts on its own and when it stops and asks, and how it speaks about decisions and money. iLang v5.0: perception sets the 11 dimensions, the frozen reference function f_v5 sets the mode, the user sees one plain line. Runs before every consequential action.
skills/judge/ on GitHub (opens in a new tab)SKILL.md -
memory
Cross-cutting: what AutoCode remembers and how every session starts. Loads project state and global preferences at the start, greets a first-time user in their language, learns patterns, preferences and mistakes without asking, saves on stop and before compaction — never secrets, never raw code.
skills/memory/ on GitHub (opens in a new tab)SKILL.md -
plan
S3 of see-it-ship-it: cut the work into steps that each end in something the person can click, with minutes not hours, core before polish, risks and costs flagged, free alternatives first. Internal planning is written in iLang; the person never sees it.
skills/plan/ on GitHub (opens in a new tab)SKILL.md -
product-study
Study an existing product from its public pages and turn it into an evidence-backed blueprint plus an MVP cut that AutoCode can build and ship. Use this whenever the user wants something "like X", "similar to X", "my own version of X", "a clone of X", names a competitor they admire, or pastes a product URL and asks to build it — even when they never say "research" or "analyze". Public sources onl…
skills/product-study/ on GitHub (opens in a new tab)SKILL.md -
security
Auto-apply security basics and block deploys that would leak secrets. Never ask the user about security choices — just do it, and run a real secret scan before going live.
skills/security/ on GitHub (opens in a new tab)SKILL.md -
see
S1 of see-it-ship-it: understand what the person wants from the way they said it. Classify intent silently, detect their level from the first messages, size the task, lock what they confirmed, and ask at most one question that is theirs to answer.
skills/see/ on GitHub (opens in a new tab)SKILL.md -
ship
S6 of see-it-ship-it: put it at a public URL. Secret scan first; static builds go to GitHub Pages at no cost (sign-up guide, device-code login, one question: it will be public); a server only when a backend is needed, cost asked once; then open the URL, rerun the acceptance on the live page, bind a domain if they want one.
skills/ship/ on GitHub (opens in a new tab)SKILL.md -
verify
S5 of see-it-ship-it: prove it works before saying so. Silent quality checks after every feature, a full review of every file before save and deploy, and the acceptance table (check / expected / actual / match) run on the local build and again on the live URL. Never 'tests passed'.
skills/verify/ on GitHub (opens in a new tab)SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.