opscale-setup 1.0.0

package/src/templates/skills/pr-description.md

@@ -0,0 +1,61 @@
+# pr-description
+
+Write a pull request title and description for the current branch. Reads the
+git diff and commit log automatically — no manual input needed.
+
+## How to use
+
+```
+/pr-description                 # draft title + body for current branch
+/pr-description --post          # draft and open the PR via gh CLI
+/pr-description --fix           # draft a fix PR
+```
+
+## Steps to follow
+
+1. Run `git log main..HEAD --oneline` to see all commits on this branch.
+2. Run `git diff main...HEAD --stat` to see changed files.
+3. Run `git diff main...HEAD` on key changed files to understand the changes.
+4. Draft the PR.
+
+## PR format
+
+```markdown
+## Summary
+<!-- 2-4 bullet points: what changed and why. Focus on intent, not mechanics. -->
+- ...
+
+## Changes
+<!-- File-level breakdown for reviewers. -->
+- `src/auth.ts` — added JWT refresh token rotation
+- `tests/auth.test.ts` — integration tests for refresh flow
+
+## Testing
+<!-- How was this tested? What should reviewers verify manually? -->
+- [ ] Unit tests pass (`npm test`)
+- [ ] Manually tested login → refresh → logout flow
+- [ ] Checked token expiry edge case with clock skew
+
+## Breaking changes
+<!-- None, or describe migration steps. -->
+None.
+
+## Related
+<!-- Issues, Slack threads, design docs — link them. -->
+Closes #...
+```
+
+## Title rules
+
+- Under 72 characters
+- Conventional Commits format: `type(scope): description`
+- Types: `feat` · `fix` · `refactor` · `test` · `docs` · `chore` · `perf`
+- Present tense, imperative mood: "add X" not "added X" or "adding X"
+- No period at the end
+
+## Rules
+
+- Do not invent changes that are not in the diff.
+- Do not describe the code — describe the intent and impact.
+- If a breaking change exists, make it impossible to miss (bold or separate section).
+- Keep the summary scannable in 30 seconds.

package/src/templates/skills/test-generation.md

@@ -0,0 +1,56 @@
+# test-generation
+
+Generate a complete, runnable test suite for a specified function, module, or
+feature. Tests must be production-quality — not stubs or placeholders.
+
+## How to use
+
+```
+/test-generation src/utils/pricing.ts
+/test-generation src/api/auth.ts --integration
+/test-generation "the checkout flow"
+```
+
+## What to generate
+
+### Unit tests (default)
+- One `describe` block per function or class
+- One `it`/`test` per distinct behavior (not per line of code)
+- Cover: happy path, edge cases, error cases, boundary values
+- Prefer `expect(result).toEqual(expected)` over implementation assertions
+- Do NOT mock internal modules — only mock at system boundaries (network, DB, time)
+
+### Integration tests (when `--integration` flag given)
+- Hit real database / real service — no mocks
+- Set up and tear down test data in `beforeEach`/`afterEach`
+- Test the full request/response cycle for API routes
+- Assert on final state, not intermediate steps
+
+## Test structure template
+
+```ts
+describe('functionName', () => {
+  it('returns X when Y', () => {
+    // Arrange
+    const input = ...;
+    // Act
+    const result = functionName(input);
+    // Assert
+    expect(result).toEqual(...);
+  });
+
+  it('throws when Z', () => {
+    expect(() => functionName(null)).toThrow(SomeError);
+  });
+});
+```
+
+## Rules
+
+- Match the test framework already used in the project (Jest, Vitest, pytest, Go
+  testing, Rust `#[test]`) — do not introduce a new one.
+- Tests must pass on a clean checkout with no additional setup.
+- Name tests so that a failing test message explains the bug without reading code.
+- If the function under test has a bug, write the test to document the correct
+  behavior (the test will fail — note this explicitly).
+- Never test private/internal implementation details.

package/src/wizard.js

@@ -0,0 +1,62 @@
+import inquirer from 'inquirer';
+import chalk from 'chalk';
+
+const PROJECT_TYPES = [
+  { name: 'Node.js / TypeScript', value: 'node' },
+  { name: 'Python', value: 'python' },
+  { name: 'Go', value: 'go' },
+  { name: 'Rust', value: 'rust' },
+  { name: 'Java / Kotlin', value: 'java' },
+  { name: 'Ruby on Rails', value: 'ruby' },
+  { name: 'Full-stack (monorepo)', value: 'fullstack' },
+  { name: 'Other / Generic', value: 'generic' },
+];
+
+const TEAM_SIZES = [
+  { name: 'Solo developer', value: 'solo' },
+  { name: 'Small team  (2–10)', value: 'small' },
+  { name: 'Medium team (11–50)', value: 'medium' },
+  { name: 'Large org   (50+)', value: 'large' },
+];
+
+const DEPLOY_TARGETS = [
+  { name: 'AWS (EC2 / ECS / Lambda)', value: 'aws' },
+  { name: 'Google Cloud (GKE / Cloud Run)', value: 'gcp' },
+  { name: 'Azure', value: 'azure' },
+  { name: 'Vercel / Netlify', value: 'vercel' },
+  { name: 'Kubernetes (self-managed)', value: 'k8s' },
+  { name: 'Docker / Docker Compose', value: 'docker' },
+  { name: 'Bare metal / VPS', value: 'vps' },
+  { name: 'Not sure yet', value: 'generic' },
+];
+
+export async function runWizard() {
+  console.log(chalk.bold('  Answer 3 quick questions to tailor your setup:\n'));
+
+  const answers = await inquirer.prompt([
+    {
+      type: 'list',
+      name: 'projectType',
+      message: 'What type of project is this?',
+      choices: PROJECT_TYPES,
+      prefix: '  1.',
+    },
+    {
+      type: 'list',
+      name: 'teamSize',
+      message: 'How large is your team?',
+      choices: TEAM_SIZES,
+      prefix: '  2.',
+    },
+    {
+      type: 'list',
+      name: 'deployTarget',
+      message: 'Where do you deploy?',
+      choices: DEPLOY_TARGETS,
+      prefix: '  3.',
+    },
+  ]);
+
+  console.log('');
+  return answers;
+}