Commit Graph

3 Commits

Author SHA1 Message Date
Pablo Estevez
5ed767ff9a run ruff 2026-01-17 17:29:21 +00:00
yusyus
c89f059712 feat(v2.7.0): Smart Rate Limit Management & Multi-Token Configuration
Major Features:
- Multi-profile GitHub token system with secure storage
- Smart rate limit handler with 4 strategies (prompt/wait/switch/fail)
- Interactive configuration wizard with browser integration
- Configurable timeout (default 30 min) per profile
- Automatic profile switching on rate limits
- Live countdown timers with real-time progress
- Non-interactive mode for CI/CD (--non-interactive flag)
- Progress tracking and resume capability (skeleton)
- Comprehensive test suite (16 tests, all passing)

Solves:
- Indefinite waiting on GitHub rate limits
- Confusing GitHub token setup

Files Added:
- src/skill_seekers/cli/config_manager.py (~490 lines)
- src/skill_seekers/cli/config_command.py (~400 lines)
- src/skill_seekers/cli/rate_limit_handler.py (~450 lines)
- src/skill_seekers/cli/resume_command.py (~150 lines)
- tests/test_rate_limit_handler.py (16 tests)

Files Modified:
- src/skill_seekers/cli/github_fetcher.py (rate limit integration)
- src/skill_seekers/cli/github_scraper.py (--non-interactive, --profile flags)
- src/skill_seekers/cli/main.py (config, resume subcommands)
- pyproject.toml (version 2.7.0)
- CHANGELOG.md, README.md, CLAUDE.md (documentation)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-17 18:38:31 +03:00
yusyus
9142223cdd refactor: Make force mode DEFAULT ON with --no-force flag to disable
BREAKING CHANGE: Force mode is now ON by default (was OFF by default)

User requested: "make this default on with skip flag only"

Changes:
--------
- Force mode is now ON by default (skip all confirmations)
- New flag: `--no-force` to disable force mode (enable confirmations)
- Old flag: `--force` removed (force is always ON now)

Rationale:
----------
- Maximizes automation out-of-the-box
- Better UX for CI/CD and batch processing (no extra flags needed)
- Aligns with "dangerously skip mode" user request
- Explicit opt-out is better than hidden opt-in for automation tools

Migration:
----------
- Before: `skill-seekers enhance output/react/ --force`
- After: `skill-seekers enhance output/react/` (force ON by default!)
- To disable: `skill-seekers enhance output/react/ --no-force`

Behavior:
---------
- Default: `LocalSkillEnhancer(skill_dir, force=True)`
- With --no-force: `LocalSkillEnhancer(skill_dir, force=False)`

CLI Examples:
-------------
# Force ON (default - no flag needed)
skill-seekers enhance output/react/

# Force OFF (enable confirmations)
skill-seekers enhance output/react/ --no-force

# Background with force (force already ON by default)
skill-seekers enhance output/react/ --background

# Background without force (need --no-force)
skill-seekers enhance output/react/ --background --no-force

Files Changed:
--------------
- src/skill_seekers/cli/enhance_skill_local.py
  - Changed default: force=False → force=True
  - Changed flag: --force → --no-force
  - Updated docstring
  - Updated help text

- src/skill_seekers/cli/main.py
  - Changed flag: --force → --no-force
  - Updated argument forwarding

- docs/ENHANCEMENT_MODES.md
  - Updated Force Mode section (default ON)
  - Updated examples (removed unnecessary --force flags)
  - Updated batch enhancement example
  - Updated CI/CD example

- CHANGELOG.md
  - Updated "Force Mode" description (Default ON)
  - Clarified no flag needed

Impact:
-------
-  CI/CD pipelines: No extra flags needed (force ON by default)
-  Batch processing: Cleaner commands
-  Manual users: Use --no-force if they want confirmations
-  Backward compatible: Old behavior available via --no-force

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-03 23:42:56 +03:00