Archived Jira-era skills: jira-ticket, draft-ticket, github-issue and project-wiki. Install only for a Jira team.
Plugin cj-jira from marketplace cj-stack in cpeaustriajc/cj-stack. Commands read from the repo's manifest — 18 days ago.
draft-ticketEnd-to-end workflow for drafting or revising a Jira ticket — draft locally, sweep test categories, gate through qa-ac-critic until clean, route engineering detail to GitHub. Use when asked to write, revise, or fix a ticket (a key, a URL, or "draft a story for X").
github-issueCreating or updating the GitHub Issues that hold implementation detail (engineering context) for this project's Jira tickets — field names, probe data, architecture, latency budgets. Use whenever technical detail needs a home, a Jira draft contains implementation content, or issues/milestones/sub-is
jira-ticketWriting or editing Jira tickets, stories, bugs, epics, or acceptance criteria for this project. Use before drafting any Jira issue title or description.
linear-planningShaping work in Linear — where a spec, feature, story, acceptance criterion, dependency or risk lands (initiative, project, spec document, phase milestone, issue), and who owns each level. Use before creating or restructuring any Linear project, milestone or issue, when a PO spec arrives as one larg
linear-projectDraft, audit, create, or update Linear projects, including translating Jira epics or product briefs into outcome-sized projects. Use for project descriptions, project properties, milestones, dependencies, lifecycle, and project updates; do not use for issue-sized work.
project-wikiKeep a repo's GitHub wiki: the decisions log (one "Decision NNN <Topic>" page per decision, indexed newest first) and the research pages behind it. Use when recording or changing a decision, moving rationale, evidence or history out of CLAUDE.md, .claude/rules or README, writing up research, or when
In-progress skills, not yet shipped in cj-stack: bug-hunt, self-verify, recall, triage, why, principles, how, architect, implement, blast-radius, unslop, ketchup, teach, no-comments, bro and microinteraction. Expect changes.
20 skills
vision, shape and tickets for top-down planning in any tracker, grill, project-knowledge and hone; break-it, ui-polish, feature-files, playbooks and interrogate for proving the work; /commit and /create-pr for the terminal.
13 skills
painting-craft: drawing and painting scenes, figures and vehicles in code (SVG, canvas, numpy, Blender) with a screenshot review loop.
1 skill
Keeps secret values out of Claude's context: redacts tool output, filters Bash streams, and denies commands that would encode, test or exfiltrate a secret
hooks
Cuts a long successful Bash output to its first 2,000 and last 3,000 characters with a cut count; read-like commands, failures and saved outputs pass whole.
Says which rule blocked an action in auto mode and the allow rule that would cover it
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.