Fixed ticker refiner labels
All checks were successful
Publish Library / Build NPM Project (push) Successful in 7s
Publish Library / Tag Version (push) Successful in 9s

This commit is contained in:
2025-12-30 20:33:19 -05:00
parent 078892297e
commit 57bbc1fdb4
2 changed files with 4 additions and 4 deletions

View File

@@ -1,6 +1,6 @@
{
"name": "@ztimson/ai-agents",
"version": "0.0.6",
"version": "0.0.7",
"description": "AI agents",
"keywords": ["ai", "review"],
"author": "ztimson",

View File

@@ -90,7 +90,7 @@ Implementation details, constraints, dependencies, design decisions
tools: [{
name: 'title',
description: 'Set the ticket title, must be called EXACTLY ONCE',
args: {title: {type: 'string', description: 'Ticket title, must match format: [Module] - [Verb] [noun]', required: true}},
args: {title: {type: 'string', description: 'Ticket title, must match format: Module - Verb noun', required: true}},
fn: (args) => title = args.title
}, {
name: 'type',
@@ -103,7 +103,7 @@ Implementation details, constraints, dependencies, design decisions
**MANDATORY STEPS:**
1. Identify ticket type: Bug, DevOps, Document, Enhancement, Refactor, or Security
2. Call \`type\` tool EXACTLY ONCE with the type from step 1
3. Call \`title\` tool EXACTLY ONCE in format: "[Module] - [Verb] [subject]"
3. Call \`title\` tool EXACTLY ONCE in format: "[Module] - [Verb] [subject]" (example: Storage - fix file uploads)
4. Output formatted markdown matching template structure below
**TEMPLATE RULES:**
@@ -166,7 +166,7 @@ Output ONLY markdown. No explanations, labels, or extra formatting.`});
'Authorization': `token ${auth}`,
'Content-Type': 'application/json'
},
body: JSON.stringify([`Kind/${type[0].toUpperCase() + type.slice(1).toLowerCase()}`])
body: JSON.stringify({labels: [`Kind/${type[0].toUpperCase() + type.slice(1).toLowerCase()}`]})
});
if(!resp.ok) throw new Error(`${resp.status} ${await resp.text()}`);
}