squirrel
Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.
- License 许可
- Apache-2.0
- 所属仓库
- ASoudy/AGS
- 最近更新
- 2026-05-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- squirrel
- risk
- safe
- tags
- [ "development", "testing", "planning", "code-review", "documentation", "ci-cd" ]
- tools
- [ "claude", "cursor", "codex", "antigravity", "gemini", "windsurf", "opencode", "copilot" ]
- author
- flying_squirrel__
- source
- community
- license
- Apache-2.0
- category
- development
- date_added
- 2026-04-29
- description
- Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.
- source_repo
- flyingsquirrel0419/squirrel-skill
- source_type
- community
- license_source
- https://github.com/flyingsquirrel0419/squirrel-skill/blob/main/LICENSE
03 SKILL.md 正文
Squirrel — Full-Cycle Software Development Skill
Overview
Squirrel is a full-cycle AI coding skill that works across 9 AI coding agents. It auto-detects project state (greenfield, in-progress, or mature) and adapts its 8-phase engineering pipeline accordingly. Instead of a one-size-fits-all workflow, it figures out where the project actually is and jumps in at exactly the right point.
When to Use This Skill
- Use when starting a new project from scratch (greenfield)
- Use when improving an existing codebase (in-progress or mature)
- Use when fixing bugs, adding features, or refactoring
- Use when adding tests, linting, or CI/CD to a project
- Use when writing production-grade documentation
- Use when the user says "build me", "fix this", "squirrel this project", or any multi-step development task
How It Works
Step 0: Detect Mode
Squirrel classifies the project directory:
| Signal | Mode | Entry Point |
|---|---|---|
| Empty directory | Greenfield | All 8 phases from scratch |
| Source files, no tests/docs | In-Progress | Audit first, then improve |
| Source + tests + CI + README | Mature | Targeted improvements |
| "fix this bug / add feature" | Targeted | Scoped work only |
The 8-Phase Pipeline
- Discover — Understand the project (audit existing code or gather requirements)
- Plan — Concrete task list with dependencies and done-criteria
- Build — Write or modify code (parallel sub-agents when supported)
- Test — Run existing tests, write new ones, 70%+ coverage target
- Bug Hunt — Static analysis + manual review
- Polish — Lint, format, type check, remove dead code
- Document — README + inline docs (update existing, don't overwrite)
- Ship — Final checklist: tests green, no secrets, CI configured
Failure Recovery (3-Strike Rule)
- Strike 1: Fix the specific error. Run tests. Move on.
- Strike 2: Re-read the code. Try a different approach.
- Strike 3: STOP. Revert. Document what failed. Ask the user.
Examples
Example 1: Build a REST API
> build me a REST API for a todo app with TypeScript and Express
Squirrel auto-detects greenfield mode and runs all 8 phases.
Example 2: Fix a bug
> fix this bug in src/auth/login.py
Squirrel enters targeted mode — abbreviated audit, scoped fix, verify.
Example 3: Improve existing project
> squirrel this project — add tests, fix lint errors, write README
Squirrel audits the existing codebase, then applies phases 4-8.
Best Practices
- Respects existing code — matches naming conventions, test framework, import style, and architecture
- Reads 2-3 similar files before writing a new one
- Never suppresses type errors with
as anyor@ts-ignore - Never deletes failing tests to "pass"
- Never leaves code in a broken state
Platform Compatibility
Squirrel works on: Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Windsurf, OpenCode, Aider (9 total).
Install with:
# Universal installer
npx skills add flyingsquirrel0419/squirrel-skill
Limitations
- Does not replace environment-specific validation or expert review
- CI/CD templates are starting points, not drop-in guarantees
- Parallel sub-agent execution depends on platform support
Related Skills
@brainstorming- For planning before implementation@test-driven-development- For TDD-oriented workflows@systematic-debugging- For methodical problem-solving
04 同仓库更多 Skills
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.
ux-heuristics
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.
system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
storybrand-messaging
Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.