naps62/yolo
home/common/programs/claude/skills/yolo/SKILL.md
Pick a Linear task (or create one), implement in a worktree, push directly with minimal ceremony
$ install --global
skillsauthnpx skillsauth add naps62/nixos-config yoloInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 11:02 AM160.5s1 file scanned
SKILL.md
- name:
- yolo
- description:
- A Linear issue ID (e.g. ERN-347), an ad-hoc task description, or omit to auto-pick next unblocked task
- user-invocable:
- true
- - name:
- input
- required:
- false
Yolo - Quick Ship Flow
Fast autonomous workflow: Linear issue -> worktree -> implementation -> push -> done. No PRs, no reviews.
First: Read ~/.claude/skills/linear-common/COMMON.md for shared setup instructions.
Workflow
1. Setup (from COMMON.md)
- Load project config
- Select task (from
$ARGUMENTS) - Set up worktree
- Gather context
2. Implement
Follow the implementation guidelines from COMMON.md. Move fast — this is yolo mode.
- Skip formal planning. Read the issue, understand it, start coding.
- Still write tests if the project has them, but don't block on edge cases.
- Run the
buildCommandif configured. If it fails, fix it. If a failure is minor and unrelated to your change, warn the user but keep going.
3. Ship
- Push the branch:
git push -u origin <branch> - If the work is complete and self-contained, merge to the default branch:
Only do this if the change is clearly ready. If unsure, just push the branch and let the user decide.git checkout <defaultBranch> git merge <branch> --no-edit git push git checkout <branch> - Move the Linear issue to "Done".
- That's it. No PR, no review loop.
Related Skills
naps62/vercel-react-best-practices
development
VerifiedTrustedCommunity
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
1SKILL.mdUpdated Apr 23, 2026
naps62/react-patterns
development
VerifiedTrustedCommunity
React component patterns with TypeScript examples. Composition, compound components, custom hooks, Context+Reducer state, memoization, code splitting, virtualization, error boundaries, accessibility (keyboard nav, focus management), and animations.
1SKILL.mdUpdated Apr 23, 2026
naps62/planning-with-files
data-ai
VerifiedTrustedCommunity
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
1SKILL.mdUpdated Apr 23, 2026
naps62/git-master
development
VerifiedTrustedCommunity
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with delegate_task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
1SKILL.mdUpdated Apr 23, 2026