@deimoscloud/coreai 0.1.9 → 0.1.11

package/src/skills/templates.ts

@@ -1,520 +0,0 @@
-/**
- * Built-in Skill Templates
- *
- * Core skill templates that are included with CoreAI.
- * These templates use {{VARIABLE}} placeholders for substitution.
- */
-
-import type { SkillTemplate } from './types.js';
-
-/**
- * Check inbox skill - process incoming messages
- */
-export const checkInboxSkill: SkillTemplate = {
-  name: 'check-inbox',
-  description: 'Check your inbox for pending tasks and messages',
-  category: 'core',
-  content: `---
-description: Check your inbox for pending tasks and messages
----
-
-# Check Inbox
-
-Check the inbox at \`KnowledgeLibrary/{{AGENT_NAME}}/inbox/\` for new messages.
-
-## Instructions
-
-1. Read all unprocessed messages in the inbox directory
-2. For each message:
-   - Parse the frontmatter (type, from, date, priority)
-   - Understand the request or task
-   - Take appropriate action based on message type
-3. After processing, move message to \`inbox/processed/\`
-4. Update your context file at \`KnowledgeLibrary/{{AGENT_NAME}}/context/current.txt\`
-
-## Message Types
-
-- **task-assignment**: New work assigned to you
-- **completion-report**: Another agent completed work
-- **review-request**: Code review needed
-- **feedback**: Response to your previous work
-
-## Output Format
-
-Report what messages were processed and actions taken.
-`,
-};
-
-/**
- * Delegate skill - assign tasks to other agents
- */
-export const delegateSkill: SkillTemplate = {
-  name: 'delegate',
-  description: 'Delegate a task to another agent via inbox messaging',
-  argumentHint: '<task-description> to <agent-name>',
-  category: 'core',
-  content: `---
-description: Delegate a task to another agent via inbox messaging
-argument-hint: <task-description> to <agent-name>
----
-
-# Delegate Task
-
-Delegate work to another agent using the inbox-based messaging system.
-
-## CRITICAL: Do NOT use the Task tool
-
-Agent-to-agent delegation MUST use file-based messaging, not the Task tool.
-The Task tool spawns subagents that lose MCP access.
-
-## Instructions
-
-1. Parse the delegation request to identify:
-   - The task to delegate
-   - The target agent
-
-2. Create a message file in the target agent's inbox:
-   - Path: \`KnowledgeLibrary/<target-agent>/inbox/\`
-   - Filename: \`YYYYMMDD_HHMM-{{AGENT_NAME}}-<subject>.md\`
-
-3. Use this message format:
-\`\`\`markdown
----
-type: task-assignment
-from: {{AGENT_NAME}}
-to: <target-agent>
-date: YYYY-MM-DD HH:MM
-priority: P2
----
-
-## Task Assignment
-
-### Description
-<Clear description of what needs to be done>
-
-### Context
-<Any relevant context or background>
-
-### Expected Deliverables
-1. <Deliverable 1>
-2. <Deliverable 2>
-
-### Success Criteria
-- <Criterion 1>
-- <Criterion 2>
-\`\`\`
-
-4. Tell the user to invoke the target agent:
-   "Please invoke @<target-agent> to process this task."
-
-## Output
-
-Confirm the delegation message was created and instruct user to invoke the agent.
-`,
-};
-
-/**
- * Git commit skill - quality-gated commits
- */
-export const gitCommitSkill: SkillTemplate = {
-  name: 'git-commit',
-  description: 'Create a quality-gated git commit',
-  argumentHint: '<commit-message>',
-  category: 'core',
-  dependencies: [{ type: 'git', required: false, description: 'For commit operations' }],
-  content: `---
-description: Create a quality-gated git commit
-argument-hint: <commit-message>
-optional: [git]
----
-
-# Git Commit
-
-Create a git commit after passing all quality gates.
-
-## Quality Gates
-
-Run these checks before committing:
-
-1. **Lint**: \`{{LINT_CMD}}\`
-2. **Tests**: \`{{TEST_CMD}}\`
-3. **Build**: \`{{BUILD_CMD}}\`
-
-## Instructions
-
-1. Stage the relevant files with \`git add\`
-2. Run all quality gate commands
-3. If any gate fails:
-   - Fix the issues
-   - Re-run the failed gate
-   - Continue only when all pass
-4. Create the commit with the provided message
-5. Format: Include ticket reference if applicable
-
-## Commit Message Format
-
-\`\`\`
-<type>(<scope>): <description>
-
-[optional body]
-
-[optional footer]
-\`\`\`
-
-Types: feat, fix, docs, style, refactor, test, chore
-
-## Fallbacks
-
-If quality gate commands are not configured:
-- Ask the user what commands to run
-- Or skip gates with user confirmation
-`,
-};
-
-/**
- * PR create skill - create pull requests
- */
-export const prCreateSkill: SkillTemplate = {
-  name: 'pr-create',
-  description: 'Create a pull request with proper format',
-  argumentHint: '[branch-name]',
-  category: 'core',
-  dependencies: [{ type: 'git', required: true, description: 'For PR creation' }],
-  content: `---
-description: Create a pull request with proper format
-argument-hint: [branch-name]
-requires: [git]
----
-
-# Create Pull Request
-
-Create a well-formatted pull request for the current branch.
-
-## Instructions
-
-1. Ensure all changes are committed
-2. Push the branch to remote
-3. Create PR with proper format:
-
-\`\`\`markdown
-## Summary
-<Brief description of changes>
-
-## Changes
-- <Change 1>
-- <Change 2>
-
-## Test Plan
-- [ ] <Test case 1>
-- [ ] <Test case 2>
-
-## Related Issues
-Closes {{JIRA_PROJECT}}-XXX
-\`\`\`
-
-4. Request reviewers if specified
-
-## Using GitHub CLI
-
-\`\`\`bash
-gh pr create --title "<title>" --body "<body>"
-\`\`\`
-
-## Output
-
-Provide the PR URL and summary of what was created.
-`,
-};
-
-/**
- * Review skill - code review delegation
- */
-export const reviewSkill: SkillTemplate = {
-  name: 'review',
-  description: 'Request or perform a code review',
-  argumentHint: '<pr-number-or-url>',
-  category: 'core',
-  dependencies: [{ type: 'git', required: true, description: 'For PR review' }],
-  content: `---
-description: Request or perform a code review
-argument-hint: <pr-number-or-url>
-requires: [git]
----
-
-# Code Review
-
-Review a pull request or delegate review to a specialist.
-
-## Instructions
-
-### If you are reviewing:
-
-1. Fetch the PR details and diff
-2. Review for:
-   - Code quality and style
-   - Logic errors or bugs
-   - Security concerns
-   - Test coverage
-   - Documentation
-3. Provide feedback with specific line references
-4. Approve, request changes, or comment
-
-### If delegating to a reviewer:
-
-1. Identify the appropriate reviewer based on the changes
-2. Create a review request message in their inbox
-3. Include PR link and context
-
-## Review Checklist
-
-- [ ] Code follows project conventions
-- [ ] No obvious bugs or edge cases
-- [ ] Tests cover the changes
-- [ ] Documentation updated if needed
-- [ ] No security vulnerabilities
-
-## Output
-
-Provide review summary with actionable feedback.
-`,
-};
-
-/**
- * Sprint status skill - check sprint progress
- */
-export const sprintStatusSkill: SkillTemplate = {
-  name: 'sprint-status',
-  description: 'Get current sprint status and progress',
-  category: 'optional',
-  dependencies: [{ type: 'issue_tracker', required: true, description: 'For sprint data' }],
-  content: `---
-description: Get current sprint status and progress
-requires: [issue_tracker]
----
-
-# Sprint Status
-
-Get the current sprint status and team progress.
-
-## Instructions
-
-1. Query the active sprint for project {{JIRA_PROJECT}}
-2. Gather metrics:
-   - Total story points committed
-   - Points completed
-   - Points in progress
-   - Points remaining
-3. List tickets by status
-4. Identify blockers or at-risk items
-
-## Output Format
-
-\`\`\`
-Sprint: <sprint-name>
-Progress: XX/YY points (ZZ%)
-
-## Completed
-- [{{JIRA_PROJECT}}-123] Task name (3 pts)
-
-## In Progress
-- [{{JIRA_PROJECT}}-124] Task name (5 pts) - @assignee
-
-## To Do
-- [{{JIRA_PROJECT}}-125] Task name (2 pts)
-
-## Blocked
-- [{{JIRA_PROJECT}}-126] Task name - Reason
-\`\`\`
-
-## Fallbacks
-
-If issue tracker is unavailable:
-- Report that sprint data cannot be fetched
-- Suggest checking the issue tracker directly at {{JIRA_URL}}
-`,
-};
-
-/**
- * Jira create skill - create Jira tickets
- */
-export const jiraCreateSkill: SkillTemplate = {
-  name: 'jira-create',
-  description: 'Create a new Jira ticket',
-  argumentHint: '<ticket-type> <summary>',
-  category: 'optional',
-  dependencies: [{ type: 'issue_tracker', required: true, description: 'For ticket creation' }],
-  content: `---
-description: Create a new Jira ticket
-argument-hint: <ticket-type> <summary>
-requires: [issue_tracker]
----
-
-# Create Jira Ticket
-
-Create a new ticket in project {{JIRA_PROJECT}}.
-
-## Instructions
-
-1. Parse the ticket type and summary from arguments
-2. Gather additional details:
-   - Description
-   - Priority
-   - Labels
-   - Components (if applicable)
-3. Create the ticket via the issue tracker integration
-4. Return the ticket key and URL
-
-## Ticket Types
-
-- **Story**: User-facing feature
-- **Bug**: Defect to fix
-- **Task**: Technical work
-- **Spike**: Research/investigation
-
-## Output
-
-\`\`\`
-Created: {{JIRA_PROJECT}}-XXX
-URL: {{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XXX
-Summary: <summary>
-Type: <type>
-\`\`\`
-
-## Fallbacks
-
-If issue tracker is unavailable:
-- Provide the user with manual creation instructions
-- Include all details they should enter
-`,
-};
-
-/**
- * Jira transition skill - update ticket status
- */
-export const jiraTransitionSkill: SkillTemplate = {
-  name: 'jira-transition',
-  description: 'Transition a Jira ticket to a new status',
-  argumentHint: '<ticket-key> to <status>',
-  category: 'optional',
-  dependencies: [{ type: 'issue_tracker', required: true, description: 'For ticket transitions' }],
-  content: `---
-description: Transition a Jira ticket to a new status
-argument-hint: <ticket-key> to <status>
-requires: [issue_tracker]
----
-
-# Transition Jira Ticket
-
-Update the status of a ticket in {{JIRA_PROJECT}}.
-
-## Status Mapping
-
-| Workflow Status | Jira Status |
-|-----------------|-------------|
-| BACKLOG | Backlog |
-| IN_PROGRESS | In Progress |
-| PR_CREATED | In Review |
-| IN_REVIEW | In Review |
-| APPROVED | Ready to Merge |
-| MERGED | Done |
-| DONE | Done |
-
-## Instructions
-
-1. Parse ticket key and target status
-2. Validate the transition is allowed
-3. Add a comment explaining the transition
-4. Execute the transition
-
-## Transition Comment Format
-
-\`\`\`
-Status updated to <status>.
-<optional context about why>
-\`\`\`
-
-## Fallbacks
-
-If issue tracker is unavailable:
-- Instruct user to manually transition at {{JIRA_URL}}
-- Provide the target status name
-`,
-};
-
-/**
- * Docs update skill - update documentation
- */
-export const docsUpdateSkill: SkillTemplate = {
-  name: 'docs-update',
-  description: 'Update project documentation',
-  argumentHint: '<doc-path-or-topic>',
-  category: 'optional',
-  dependencies: [{ type: 'documentation', required: false, description: 'For remote docs' }],
-  content: `---
-description: Update project documentation
-argument-hint: <doc-path-or-topic>
-optional: [documentation]
----
-
-# Update Documentation
-
-Update project documentation for a specific topic or file.
-
-## Instructions
-
-1. Identify the documentation to update:
-   - Local: \`{{DOCS_PATH}}/\`
-   - Remote: {{CONFLUENCE_SPACE}} (if configured)
-
-2. Make the necessary updates:
-   - Keep formatting consistent
-   - Update examples if code changed
-   - Add/update version information
-
-3. For remote documentation:
-   - Use the documentation integration
-   - Or provide content for manual update
-
-## Documentation Types
-
-- **README**: Project overview and setup
-- **API Docs**: Endpoint documentation
-- **Architecture**: Design decisions
-- **Runbooks**: Operational procedures
-
-## Fallbacks
-
-If documentation integration is unavailable:
-- Create/update local markdown files
-- Provide instructions for manual remote update
-`,
-};
-
-/**
- * All built-in skill templates
- */
-export const builtInSkills: SkillTemplate[] = [
-  checkInboxSkill,
-  delegateSkill,
-  gitCommitSkill,
-  prCreateSkill,
-  reviewSkill,
-  sprintStatusSkill,
-  jiraCreateSkill,
-  jiraTransitionSkill,
-  docsUpdateSkill,
-];
-
-/**
- * Get a skill template by name
- */
-export function getSkillTemplate(name: string): SkillTemplate | undefined {
-  return builtInSkills.find((s) => s.name === name);
-}
-
-/**
- * Get all skill templates of a category
- */
-export function getSkillsByCategory(category: 'core' | 'optional'): SkillTemplate[] {
-  return builtInSkills.filter((s) => s.category === category);
-}