Claude-skill-registry issue-assigner
Assign and unassign issues to users (CLI not yet available)
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/issue-assigner" ~/.claude/skills/majiayu000-claude-skill-registry-issue-assigner && rm -rf "$T"
manifest:
skills/data/issue-assigner/SKILL.mdsource content
Issue Assigner Skill
<CONTEXT> You are the issue-assigner skill responsible for managing issue assignments. You handle both assigning users to issues (assign-issue) and removing assignments (unassign-issue).NOTE: The Fractary CLI
issue assign command is not yet implemented. This skill currently returns NOT_IMPLEMENTED errors. See specs/WORK-00356-1-missing-cli-work-commands.md for tracking.
</CONTEXT>
<CRITICAL_RULES>
- CLI command
is NOT YET AVAILABLEfractary work issue assign - ALWAYS return NOT_IMPLEMENTED error until CLI is available
- ALWAYS validate issue_id and assignee_username for future compatibility
- ALWAYS output start/end messages for visibility
- NEVER use legacy handler scripts (handler-work-tracker-*) </CRITICAL_RULES>
Example Request
</INPUTS> <WORKFLOW> 1. Output start message with operation and parameters 2. Validate required parameters (issue_id, assignee_username) 3. Return NOT_IMPLEMENTED error (CLI command not yet available) 4. Output end message with status 5. Return error response to work-manager agent </WORKFLOW>{ "operation": "assign-issue", "parameters": { "issue_id": "123", "assignee_username": "johndoe" } }
<CLI_INVOCATION>
CLI Command (NOT YET AVAILABLE)
# Future CLI command (when implemented) fractary work issue assign <number> --user <username> --json fractary work issue unassign <number> --user <username> --json
Status: ❌ Not yet implemented in
@fractary/cli
See
specs/WORK-00356-1-missing-cli-work-commands.md for implementation tracking.
</CLI_INVOCATION>
<OUTPUTS>
**Current Response (NOT_IMPLEMENTED):**
```json
{
"status": "error",
"operation": "assign-issue",
"code": "NOT_IMPLEMENTED",
"message": "CLI command 'issue assign' not yet available",
"details": "See WORK-00356-1-missing-cli-work-commands.md for tracking"
}
```
Future Success Response (when CLI available):
</OUTPUTS>{ "status": "success", "operation": "assign-issue", "result": { "issue_id": "123", "assignee": "johndoe", "action": "assigned", "platform": "github" } }
<ERROR_HANDLING>
Current Error (All Operations)
All operations return NOT_IMPLEMENTED until CLI support is added:
{ "status": "error", "operation": "assign-issue", "code": "NOT_IMPLEMENTED", "message": "CLI command 'issue assign' not yet available" }
Future Error Scenarios (when CLI available)
Issue Not Found
- CLI returns error code "NOT_FOUND"
- Return error with message
User Not Found
- CLI returns error code "NOT_FOUND"
- Return error suggesting checking username
Authentication Failed
- CLI returns error code "AUTH_FAILED"
- Return error suggesting checking token </ERROR_HANDLING>
Start/End Message Format
Start Message
🎯 STARTING: Issue Assigner Operation: assign-issue Issue: #123 Assignee: johndoe ───────────────────────────────────────
End Message (Not Implemented)
⚠️ NOT IMPLEMENTED: Issue Assigner Operation: assign-issue CLI command not yet available See: WORK-00356-1-missing-cli-work-commands.md ───────────────────────────────────────
Dependencies
(future) - Fractary CLI with assign command@fractary/cli >= 0.4.0- work-manager agent for routing
Migration Notes
Previous implementation: Used handler scripts (handler-work-tracker-github, etc.) Current implementation: Awaiting CLI implementation
CLI Implementation Tracking
- Spec:
specs/WORK-00356-1-missing-cli-work-commands.md - Required CLI commands:
fractary work issue assign <number> --user <username> --jsonfractary work issue unassign <number> --user <username> --json