jumbleknot
@jumbleknot
Public Skills
forgejo-issues
by jumbleknot
The MCM backlog lives in this repository's Forgejo issue tracker. Use when filing, finding, updating or closing backlog items, or when deciding whether work belongs in the backlog rather than in the current change.
speckit-taskstoissues
by jumbleknot
"Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts."
speckit-plan
by jumbleknot
"Execute the implementation planning workflow using the plan template to generate design artifacts."
speckit-tasks
by jumbleknot
"Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts."
speckit-checklist
by jumbleknot
"Generate a custom checklist for the current feature based on user requirements."
speckit-implement
by jumbleknot
"Execute the implementation plan by processing and executing all tasks defined in tasks.md"
speckit-specify
by jumbleknot
"Create or update the feature specification from a natural language feature description."
speckit-agent-context-update
by jumbleknot
Refresh the managed Spec Kit section in the coding agent context file
speckit-converge
by jumbleknot
"Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it."
speckit-clarify
by jumbleknot
"Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec."
speckit-git-commit
by jumbleknot
Auto-commit changes after a Spec Kit command completes
speckit-git-initialize
by jumbleknot
Initialize a Git repository with an initial commit
speckit-analyze
by jumbleknot
"Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation."
speckit-git-feature
by jumbleknot
Create a feature branch with sequential or timestamp numbering
speckit-git-validate
by jumbleknot
Validate current branch follows feature branch naming conventions
speckit-git-remote
by jumbleknot
Detect Git remote URL for GitHub integration
nx-import
by jumbleknot
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.
link-workspace-packages
by jumbleknot
'Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager''s workspace commands to fix actual linking.'
monitor-ci
by jumbleknot
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.