How do I install the Feature skill?

Run npx skillmds@latest add openwpm/feature in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Feature safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Feature?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Feature free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Feature?

openwpm (@openwpm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Feature by openwpm — Agent Skill

Name: Feature
Author: openwpm

Feature

Use to create a `feat/<slug>` branch from a human-readable description and register a matching crosslink issue (priority medium, label `feature`). Slugifies the description, validates preconditions (no uncommitted changes, branch doesn't already exist), and checks out the new branch. Trigger when the user says "new feature branch for X", "make a feature branch", or "/feature …".

openwpm d09fd0c 2.3 KB Updated Sep 17, 2026

File contents

Feature — create a feature branch + crosslink issue

The user will provide a human-readable description of the feature (e.g. "add batch retry logic"). Create a feature branch following the project's naming convention.

1. Derive the branch name

Slugify the description: lowercase, strip non-alphanumeric characters (except hyphens), replace spaces with hyphens, collapse consecutive hyphens.
The branch name is feat/<slug> (e.g. feat/add-batch-retry-logic), matching the repo convention (e.g. feat/stealth-js-instrument-v2).
If the slug is empty or the branch already exists, ask the user for a different name.

2. Validate preconditions

Confirm there are no unexpected working-copy changes (jj status). In jj the working copy is always a commit, so changes don't block branching — but warn the user if the diff is unexpectedly large and ask whether to proceed.
Identify the base revision. Default to @ (the current change). If the user provides a --from <ref> argument, use that instead.

3. Create the bookmark

jj bookmark create feat/<slug> -r <base-ref>
jj new feat/<slug> -m "wip: start feat/<slug>"

This creates the feat/<slug> bookmark and starts a new change on top of it. Always pass -m to jj new. Print the created bookmark name so the user can confirm.

4. Track in crosslink

Create a crosslink issue for the feature work with the user's original description as the title.
Set priority to medium (unless the user specifies otherwise).
Use: crosslink issue create "<description>" -p medium --label feature

Constraints

Never force-push or delete bookmarks.
Do not push the bookmark to a remote — the user will do that when ready.
Keep the slug concise. If the description is very long, truncate to the first 6-8 meaningful words.
Always pass -m to jj commands — never let jj open an editor.

---name: featuredescription: Use to create a `feat/<slug>` branch from a human-readable description and register a matching crosslink issue (priority medium, label `feature`). Slugifies the description, validates preconditions (no uncommitted changes, branch doesn't already exist), and checks out the new branch. Trigger when the user says "new feature branch for X", "make a feature branch", or "/feature …".---# Feature — create a feature branch + crosslink issueThe user will provide a human-readable description of the feature (e.g. "add batch retry logic"). Create a feature branch following the project's naming convention.## 1. Derive the branch name- Slugify the description: lowercase, strip non-alphanumeric characters (except hyphens), replace spaces with hyphens, collapse consecutive hyphens.- The branch name is `feat/<slug>` (e.g. `feat/add-batch-retry-logic`), matching the repo convention (e.g. `feat/stealth-js-instrument-v2`).- If the slug is empty or the branch already exists, ask the user for a different name.## 2. Validate preconditions- Confirm there are no unexpected working-copy changes (`jj status`). In jj the working copy is always a commit, so changes don't block branching — but warn the user if the diff is unexpectedly large and ask whether to proceed.- Identify the base revision. Default to `@` (the current change). If the user provides a `--from <ref>` argument, use that instead.## 3. Create the bookmark```bashjj bookmark create feat/<slug> -r <base-ref>jj new feat/<slug> -m "wip: start feat/<slug>"```This creates the `feat/<slug>` bookmark and starts a new change on top of it. Always pass `-m` to `jj new`. Print the created bookmark name so the user can confirm.## 4. Track in crosslink- Create a crosslink issue for the feature work with the user's original description as the title.- Set priority to `medium` (unless the user specifies otherwise).- Use: `crosslink issue create "<description>" -p medium --label feature`## Constraints- Never force-push or delete bookmarks.- Do not push the bookmark to a remote — the user will do that when ready.- Keep the slug concise. If the description is very long, truncate to the first 6-8 meaningful words.- Always pass `-m` to jj commands — never let jj open an editor.

Frequently asked questions