@compilr-dev/agents-coding 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -29,6 +29,16 @@ export declare const projectOnboardingSkill: Skill;
29
29
  * Code optimization skill
30
30
  */
31
31
  export declare const codeOptimizationSkill: Skill;
32
+ /**
33
+ * Build skill - Implement a backlog item end-to-end
34
+ * Moved from @compilr-dev/agents because it uses run_tests, run_lint
35
+ */
36
+ export declare const buildSkill: Skill;
37
+ /**
38
+ * Scaffold skill - Create project foundation based on tech stack
39
+ * Moved from @compilr-dev/agents because it uses detect_project
40
+ */
41
+ export declare const scaffoldSkill: Skill;
32
42
  /**
33
43
  * All coding skills
34
44
  */
@@ -305,6 +305,195 @@ export const codeOptimizationSkill = defineSkill({
305
305
  tags: ['performance', 'optimization', 'workflow'],
306
306
  version: '1.0.0',
307
307
  });
308
+ /**
309
+ * Build skill - Implement a backlog item end-to-end
310
+ * Moved from @compilr-dev/agents because it uses run_tests, run_lint
311
+ */
312
+ export const buildSkill = defineSkill({
313
+ name: 'build',
314
+ description: 'Implement a backlog item end-to-end',
315
+ tags: ['implementation', 'coding'],
316
+ prompt: `You are in BUILD MODE. Implement the specified backlog item.
317
+
318
+ ## ITEM TO IMPLEMENT
319
+ - **ID:** {{item_id}}
320
+ - **Title:** {{item_title}}
321
+ - **Type:** {{item_type}}
322
+ - **Priority:** {{item_priority}}
323
+ - **Description:** {{item_description}}
324
+
325
+ ## BEFORE STARTING
326
+
327
+ 1. Show the item details to the user in a clear format
328
+ 2. Use ask_user_simple to confirm: "Proceed with implementation?"
329
+ - Options: "Yes, let's build it", "No, pick a different item", "Cancel"
330
+ 3. If there are dependency warnings, mention them and ask if user wants to proceed anyway
331
+
332
+ ## CONTEXT TO READ
333
+
334
+ Before implementing, read these files for context:
335
+ - **PRD.md** (if exists): Project vision and requirements
336
+ - **CLAUDE.md**: Coding standards and conventions
337
+ - **Existing code**: Understand patterns already in use
338
+
339
+ ## IMPLEMENTATION WORKFLOW
340
+
341
+ ### Phase 1: Plan
342
+ 1. Use todo_write to create implementation checklist:
343
+ - Break down the item into concrete tasks
344
+ - Identify files to create or modify
345
+ - Note any edge cases to handle
346
+ 2. Update backlog status to 🚧 using backlog_write
347
+
348
+ ### Phase 2: Implement
349
+ 1. Write code following project conventions from CLAUDE.md
350
+ 2. Add tests if the project has a test framework
351
+ 3. Keep changes focused on the backlog item scope
352
+ 4. Use todo_write to track progress through tasks
353
+
354
+ ### Phase 3: Verify
355
+ 1. Run tests with run_tests tool
356
+ 2. Run lint with run_lint tool
357
+ 3. If tests or lint fail:
358
+ - Analyze the error message
359
+ - Fix the issue
360
+ - Re-run verification
361
+ - Repeat up to 3 times
362
+ 4. If still failing after 3 attempts:
363
+ - Report the issue to user
364
+ - Keep status as 🚧
365
+ - Ask for guidance
366
+
367
+ ### Phase 4: Complete
368
+ 1. Update backlog status to ✅ using backlog_write
369
+ 2. Create git commit with message format:
370
+ - feat({{item_id}}): {{item_title}} - for features
371
+ - fix({{item_id}}): {{item_title}} - for bugs
372
+ - chore({{item_id}}): {{item_title}} - for chores
373
+ 3. Update backlog with the commit SHA
374
+ 4. Clear todos with todo_write
375
+ 5. Summarize what was implemented
376
+
377
+ ## RULES
378
+
379
+ - Follow coding standards from CLAUDE.md strictly
380
+ - Keep commits atomic - one backlog item per commit
381
+ - Ask user via ask_user_simple if you hit blockers
382
+ - Don't over-engineer - implement exactly what the item describes
383
+ - Don't add features beyond what was requested
384
+ - Use todo_write throughout to show progress
385
+ - Always run tests before marking complete`,
386
+ version: '1.0.0',
387
+ });
388
+ /**
389
+ * Scaffold skill - Create project foundation based on tech stack
390
+ * Moved from @compilr-dev/agents because it uses detect_project
391
+ */
392
+ export const scaffoldSkill = defineSkill({
393
+ name: 'scaffold',
394
+ description: 'Create project foundation based on tech stack',
395
+ tags: ['setup', 'foundation', 'scaffolding'],
396
+ prompt: `You are creating the PROJECT SCAFFOLD (foundation).
397
+
398
+ ## PURPOSE
399
+
400
+ Create the base project structure that features will be built on top of.
401
+ This is the skeleton that makes feature implementation possible.
402
+
403
+ ## CONTEXT TO READ
404
+
405
+ First, read these files to understand what to build:
406
+ - **CLAUDE.md**: Tech stack, coding standards, project type
407
+ - **PRD.md** (if exists): Project vision and requirements
408
+ - **Existing files**: What already exists (if anything)
409
+
410
+ ## BEFORE STARTING
411
+
412
+ 1. Summarize the detected/specified tech stack
413
+ 2. Use ask_user_simple to confirm: "Create project scaffold with this stack?"
414
+ - Options: "Yes, create it", "No, let me specify", "Cancel"
415
+ 3. If user wants to specify, ask about tech stack preferences
416
+
417
+ ## SCAFFOLD BY PROJECT TYPE
418
+
419
+ ### Web Application (React/Vue/Svelte)
420
+
421
+ Create:
422
+ - \`src/\` folder structure:
423
+ - \`src/components/\` - Reusable components
424
+ - \`src/pages/\` or \`src/routes/\` - Page components
425
+ - \`src/lib/\` or \`src/utils/\` - Utility functions
426
+ - \`src/styles/\` - Global styles
427
+ - \`package.json\` with dependencies
428
+ - Build config (\`vite.config.ts\`, \`next.config.js\`, etc.)
429
+ - \`index.html\` entry point (if applicable)
430
+ - Basic App component with routing setup
431
+ - CSS/Tailwind configuration
432
+ - \`.gitignore\`
433
+ - \`README.md\` with setup instructions
434
+
435
+ ### API / Backend (Node/Python/Go)
436
+
437
+ Create:
438
+ - \`src/\` folder structure:
439
+ - \`src/routes/\` or \`src/api/\` - API endpoints
440
+ - \`src/services/\` - Business logic
441
+ - \`src/models/\` - Data models
442
+ - \`src/utils/\` - Utilities
443
+ - \`package.json\` / \`requirements.txt\` / \`go.mod\`
444
+ - Entry point (\`src/index.ts\`, \`main.py\`, \`main.go\`)
445
+ - Basic server setup (Express, FastAPI, Gin, etc.)
446
+ - Health check endpoint (\`GET /health\`)
447
+ - Environment config (\`.env.example\`)
448
+ - \`.gitignore\`
449
+ - \`README.md\` with setup instructions
450
+
451
+ ### CLI Tool (Node/Python/Rust)
452
+
453
+ Create:
454
+ - \`src/\` folder structure:
455
+ - \`src/commands/\` - Command handlers
456
+ - \`src/utils/\` - Utilities
457
+ - \`package.json\` with \`bin\` entry / \`setup.py\` / \`Cargo.toml\`
458
+ - Entry point with argument parsing
459
+ - Basic command structure (help, version)
460
+ - \`.gitignore\`
461
+ - \`README.md\` with usage instructions
462
+
463
+ ### Full-Stack Application
464
+
465
+ Create both frontend and backend structures:
466
+ - \`frontend/\` or \`client/\` - Web app scaffold
467
+ - \`backend/\` or \`server/\` - API scaffold
468
+ - Root \`package.json\` with workspace config (if monorepo)
469
+ - \`docker-compose.yml\` (optional)
470
+ - \`.gitignore\`
471
+ - \`README.md\` with setup instructions
472
+
473
+ ## POST-SCAFFOLD STEPS
474
+
475
+ 1. Install dependencies:
476
+ - \`npm install\` / \`pip install -r requirements.txt\` / etc.
477
+ 2. Run build to verify:
478
+ - \`npm run build\` / equivalent
479
+ 3. Run lint to verify:
480
+ - \`npm run lint\` / equivalent
481
+ 4. Create initial git commit:
482
+ - \`chore: initial project scaffold\`
483
+ 5. Update backlog:
484
+ - Mark scaffold CHORE as ✅ (if exists)
485
+
486
+ ## RULES
487
+
488
+ - Follow conventions from CLAUDE.md
489
+ - Use modern, widely-adopted patterns
490
+ - Keep it minimal - only what's needed to start
491
+ - Don't add features - just structure
492
+ - Ensure the project builds and lints clean
493
+ - Add helpful comments in config files
494
+ - Include TypeScript/type hints where applicable`,
495
+ version: '1.0.0',
496
+ });
308
497
  /**
309
498
  * All coding skills
310
499
  */
@@ -315,6 +504,8 @@ export const codingSkills = [
315
504
  prWorkflowSkill,
316
505
  projectOnboardingSkill,
317
506
  codeOptimizationSkill,
507
+ buildSkill,
508
+ scaffoldSkill,
318
509
  ];
319
510
  /**
320
511
  * Export individual skills for selective use
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@compilr-dev/agents-coding",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "description": "Coding-specific tools for @compilr-dev/agents - Git, project detection, smart runners, and code search",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -49,7 +49,7 @@
49
49
  },
50
50
  "repository": {
51
51
  "type": "git",
52
- "url": "git+https://github.com/scozzola/compilr-dev-agents-coding.git"
52
+ "url": "git+https://github.com/compilr-dev/agents-coding.git"
53
53
  },
54
54
  "keywords": [
55
55
  "ai",
@@ -64,18 +64,18 @@
64
64
  "author": "Carmelo Scozzola",
65
65
  "license": "MIT",
66
66
  "bugs": {
67
- "url": "https://github.com/scozzola/compilr-dev-agents-coding/issues"
67
+ "url": "https://github.com/compilr-dev/agents-coding/issues"
68
68
  },
69
- "homepage": "https://github.com/scozzola/compilr-dev-agents-coding#readme",
69
+ "homepage": "https://github.com/compilr-dev/agents-coding#readme",
70
70
  "engines": {
71
71
  "node": ">=18.0.0"
72
72
  },
73
73
  "peerDependencies": {
74
- "@compilr-dev/agents": "^0.2.0"
74
+ "@compilr-dev/agents": "^0.3.0"
75
75
  },
76
76
  "devDependencies": {
77
77
  "@anthropic-ai/sdk": "^0.30.1",
78
- "@compilr-dev/agents": "^0.2.0",
78
+ "@compilr-dev/agents": "^0.3.0",
79
79
  "@eslint/js": "^9.39.1",
80
80
  "@types/node": "^24.10.1",
81
81
  "@vitest/coverage-v8": "^3.2.4",