feat: add --tech / -t CLI flag to force specific technologies

[Mbg999]

Add --tech / -t CLI flag to bypass auto-detection and manually specify the technologies to install skills for. Supports multiple flags (--tech react --tech nextjs) and comma-separated values (--tech react,nextjs). Unknown technology IDs emit a warning and are skipped.

When --tech is provided, the CLI builds the detected technology list directly from SKILLS_MAP instead of running the full project scan, while still evaluating combos and frontend inference from the forced IDs.

Includes tests for the new flag and updates both README files with usage documentation.

What Changed

• packages/autoskills/main.ts
  • Added technologies: string[] to CliArgs interface.
  • Extended parseArgs() to parse -t / --tech supporting multiple invocations and comma-separated values.
  • Updated showHelp() to document the new flag.
  • Modified main() to skip detectTechnologies() when --tech is present and build the detected array directly from SKILLS_MAP + FRONTEND_PACKAGES.
• packages/autoskills/tests/cli.test.ts
  • Added 5 test cases covering: single --tech, multiple flags, comma-separated syntax, unknown-tech warning, and combination with -y.
• README.md and packages/autoskills/README.md
  • Added -t, --tech to the options table.
  • Added usage example section in the package README.

Why This Change

There are greenfield projects where there are no elements yet that can be detected by heuristics, but which are intended to be added later, in addition to giving the possibility to skip it and install only what you want quickly. It also allows an agent to detect and pass on which technologies it wants to the installer.

Testing Done

• Ran the full pnpm test suite on Node.js 22.22.3 — all 364 tests pass.

• Verified that npx autoskills --dry-run --tech react outputs only React skills.

• Verified that npx autoskills --dry-run --tech react,nextjs detects both technologies and their combos.

• Verified that npx autoskills --dry-run --tech unknown prints a warning and exits cleanly.

• Manual testing completed

• Automated tests pass locally

• Edge cases considered and tested

Type of Change

• fix: Bug fix
• feat: New feature
• refactor: Code refactoring
• docs: Documentation
• test: Tests
• chore: Maintenance/tooling

Security & Quality Checklist

• No secrets or API keys committed
• Follows the project's coding standards
• No sensitive data exposed in logs or output

Documentation

• Updated relevant documentation
• Added comments for complex logic (none required — self-explanatory code)
• README updated (if needed)