skills/install-rules/SKILL.md
Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
npx skillsauth add sd0xdev/sd0x-dev-flow install-rulesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/install-hooks)/install-scripts)/project-setup)Phase 1: Locate plugin rules dir
Phase 2: Enumerate *.md
Phase 3: Determine install set (--all, specific names, or interactive)
Phase 3.5: Read manifest + classify (new/unchanged/modified/conflict)
Phase 4: Install (smart merge with manifest tracking)
Phase 4.5: Backfill CLAUDE.md references
Phase 5: Output report
$ARGUMENTS
| Argument | Description |
|----------|-------------|
| --all | Install all available rules |
| --list | List available rules without installing |
| --dry-run | Show what would be installed, no changes |
| --force | Overwrite modified rules |
| --legacy-strategy <strategy> | Handle pre-manifest installs (ask/overwrite/skip) |
| --customize <rule> | Customize a project-override rule |
| rule-names... | Specific rules to install |
Uses .sd0x/install-state.json to track installed file hashes. Smart merge logic:
| Status | Action | |--------|--------| | New (not installed) | Copy | | Unchanged (hash match) | Auto-upgrade | | Modified by user | Skip (preserve edits) | | Conflict (both changed) | AskUserQuestion |
--customize)Manages *-project.md companion files for user overrides:
| Sub-flag | Action |
|----------|--------|
| (none) | Show section status |
| --add-section | Add a new section |
| --update-section <name> | Update specific section |
| --reset | Regenerate from template |
## Install Rules Report
| Rule | Status | Action |
|------|--------|--------|
| auto-loop.md | unchanged | auto-upgraded |
| testing.md | user-modified | skipped |
Installed: N | Skipped: M | Conflicts: K
documentation
Rewrite the previous reply in Traditional Chinese
development
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
development
Verification loop — lint -> typecheck -> unit -> integration -> e2e
development
Research current code state then update corresponding docs, ensuring docs stay in sync with code.