New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Develop A Feature

by compartmentdev in compartmentdev/compartment

Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

Apache-2.0Auto-check passedBackend & APIs

Install Develop A Feature

skills CLI
$ npx skills add compartmentdev/compartment --skill develop-a-feature -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compartmentdev/compartment develop-a-feature --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compartmentdev/compartment.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/develop-a-feature .claude/skills/develop-a-feature && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
develop-a-feature
GitHub stars
205
Token cost
~554 tokens
SKILL.md length
291 words
Files
2
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

  • Works in 9 steps: If you are creating a branch from main,… → Run $preflight-feature-review with the… → Treat product behavior as CLI-first.… → …
  • Backend & APIs work in your project
  • SKILL.md covers Read and Algorithm
  • Calls pnpm

What it does

Develop A Feature is an agent skill from compartmentdev/compartment. Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs. It works with pnpm. The repository describes itself as: Compartment is a self-hosted deployment system for small software on infrastructure your team controls. The licence is Apache-2.0.

When your agent uses it

  • Backend & APIs work in your project

Example prompts

  • “/develop-a-feature”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. If you are creating a branch from main, update local main first, then create the feature branch from that updated main.
  2. Run $preflight-feature-review with the request, intended outcome, known scope, and visible constraints. Let that skill own its review…
  3. Treat product behavior as CLI-first. Before adding or changing UI behavior, find the matching CLI command and its existing SDK/API…
  4. Resolve blockers from the brief first. Then implement only in the returned owner, boundary, and canonical path.
  5. When the feature adds or changes permissions, make the default-grant and rollout decision explicit in the same change instead of leaving…
  6. Change the smallest owning surface. Do not add fallback branches, compatibility glue, silent env defaults, public/internal URL mixing…
  7. Update tests in the same diff. Prefer behavior, boundary, integration, or e2e coverage. Delete or rewrite plumbing-mirror tests instead of…
  8. After implementation, run owning-package pnpm lint, pnpm typecheck, and pnpm test when applicable, plus only the diff-triggered special…
  9. Close out with the entry file to read first, checks run, remaining unrun validation, and the user-visible verification flow.

What it can do on your machine

Read from SKILL.md and the folder at commit 15373e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Develop A Feature loads about 554 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~554

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from compartmentdev/compartment at commit 15373e7, republished under its Apache-2.0 licence (© compartmentdev). 291 words, ~554 tokens.

Download SKILL.mdSave it as .claude/skills/develop-a-feature/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
develop-a-feature
description
Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

Develop a Feature

Use for implementation work in this repo.

Read

  • AGENTS.md
  • the owning layer doc
  • docs/specs/type-placement.md only when type ownership may change
  • $preflight-feature-review

Algorithm

  1. If you are creating a branch from main, update local main first, then create the feature branch from that updated main.
  2. Run $preflight-feature-review with the request, intended outcome, known scope, and visible constraints. Let that skill own its review agents. Do not edit before its brief returns.
  3. Treat product behavior as CLI-first. Before adding or changing UI behavior, find the matching CLI command and its existing SDK/API contract. The UI must reuse that existing method, or reuse and extend that same shared method/contract when the feature genuinely needs more data. Do not add a new UI-only API route, browser-only SDK method, or parallel contract for behavior that duplicates a CLI feature.
  4. Resolve blockers from the brief first. Then implement only in the returned owner, boundary, and canonical path.
  5. When the feature adds or changes permissions, make the default-grant and rollout decision explicit in the same change instead of leaving it implicit.
  6. Change the smallest owning surface. Do not add fallback branches, compatibility glue, silent env defaults, public/internal URL mixing, export drift, or test-only seams.
  7. Update tests in the same diff. Prefer behavior, boundary, integration, or e2e coverage. Delete or rewrite plumbing-mirror tests instead of shaping production code around them.
  8. After implementation, run owning-package pnpm lint, pnpm typecheck, and pnpm test when applicable, plus only the diff-triggered special checks. Do not manually run repo-wide pnpm check, pnpm check:unused, pnpm check:unused:runtime, or pnpm check:ci unless the task explicitly requires them.
  9. Close out with the entry file to read first, checks run, remaining unrun validation, and the user-visible verification flow.

© compartmentdev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/develop-a-feature of compartmentdev/compartment.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 15373e7

Compare with similar skills

Develop A Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Develop A Feature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Develop A Feature this skillcompartmentdev/compartment205—~554Automated safety check: PassApache-2.0
WooCommerce Email Editor Developmentwoocommerce/woocommerce11k—~893Automated safety check: PassCustom licence
React Emailviclafouch/meme-studio1102 repos~3.6kAutomated safety check: PassMIT
Land TS MonoUKGovernmentBEIS/inspect_ai2.9k—~3kAutomated safety check: PassMIT
Projectlin-97/gi-demo188—~1.4kAutomated safety check: NotesApache-2.0
Validate OAuth Integrationrome-os/rome717—~2kAutomated safety check: NotesMIT

Similar skills

  • WooCommerce Email Editor Development

    woocommerce/woocommerce

    Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.

    11k GitHub stars~893 tokensUpdated today
    Backend & APIsAuto-check passed

  • React Email

    viclafouch/meme-studio

    A skill your agent uses when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.

    110 GitHub starsUsed in 2 repos~3.6k tokens
    Backend & APIsAuto-check passed

  • Land TS Mono

    UKGovernmentBEIS/inspect_ai

    Land a PR that requires a coordinated ts-mono submodule change.

    2.9k GitHub stars~3k tokensUpdated today
    Backend & APIsAuto-check passed

  • Project

    lin-97/gi-demo

    后台管理模板的项目总览与前端强制规范。涵盖 Vue 3 + Arco Design + Gi 组件库、目录结构、自动导入、CRUD/API 约定与代码风格。在当前仓库内开发、新增页面、查阅架构或不确定项目规范时使用。

    188 GitHub stars~1.4k tokensUpdated 3 mo ago
    Backend & APIsAuto-check: notes

  • Validate OAuth Integration

    rome-os/rome

    Validate a Rome-managed OAuth integration end-to-end — prove a user can click Connect and Rome ends up holding a delegated token it can use to call the provider's API.

    717 GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check: notes

  • Lerd

    liberusoftware/real-estate-laravel

    Manage the lerd local PHP development environment via MCP tools: run framework console commands (artisan, bin/console, etc.), manage services, start/stop queue workers, run composer, manage Node.js…

    112 GitHub stars~7.8k tokensUpdated 2 days ago
    Backend & APIsAuto-check: warnings

More from compartmentdev/compartment

All 12 skills in this repo

  • Audit Type Ownership

    compartmentdev/compartment

    Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

    205 GitHub stars~745 tokensUpdated 1 mo ago
    Auto-check passed

  • Open PR And Monitor

    compartmentdev/compartment

    Open or reuse a repo PR and monitor it with a five-minute Codex heartbeat until it is ready, terminal, or blocked.

    205 GitHub stars~470 tokensUpdated 1 mo ago
    Auto-check passed

  • Review A Change

    compartmentdev/compartment

    A skill your agent uses when the user invokes $review-a-change or asks for a compartment repo code review; always use the delegated subagent review path by splitting review into separate parallel…

    205 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Review Reuse And Dedup

    compartmentdev/compartment

    A skill your agent uses when reviewing compartment repo changes for existing helper reuse, extractable pure utilities, duplicated logic, repeated constants, hardcoded values, or repeated variable…

    205 GitHub stars~753 tokensUpdated 1 mo ago
    Auto-check passed

  • Compartment Smoke Test

    compartmentdev/compartment

    Run or delegate a browser-first smoke test of the local compartment through browser-use as a real user: boot or reuse the local stack, install or log in, deploy the repo smoke fixtures, verify CLI…

    205 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check: notes

  • Public Docs Maintenance

    compartmentdev/compartment

    Maintain the public Starlight docs site for material changes to shipped Compartment workflows, using generated reference where possible and concise task- and decision-focused guides elsewhere.

    205 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Develop A Feature

What does Develop A Feature do?

Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks. Develop A Feature is an agent skill from compartmentdev/compartment. Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

When should I use Develop A Feature?

Develop A Feature fits situations like: backend & APIs work in your project.

How do I install Develop A Feature in Claude Code?

Run `npx skills add compartmentdev/compartment --skill develop-a-feature -a claude-code`. Or copy the skill folder (.codex/skills/develop-a-feature in compartmentdev/compartment) into .claude/skills/develop-a-feature in your project. Claude Code loads it when a task matches its description.

How do I install Develop A Feature in Codex?

Run `npx skills add compartmentdev/compartment --skill develop-a-feature -a codex`. Or copy the skill folder (.codex/skills/develop-a-feature in compartmentdev/compartment) into .agents/skills/develop-a-feature in your project. Codex loads it when a task matches its description.

Can I use Develop A Feature in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compartmentdev/compartment --skill develop-a-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/develop-a-feature, .gemini/skills/develop-a-feature, .github/skills/develop-a-feature and .opencode/skills/develop-a-feature in your project.

What does Develop A Feature need to run?

Going by SKILL.md and its folder, Develop A Feature needs the command-line tools its instructions call (pnpm).

Does Develop A Feature access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Develop A Feature safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Develop A Feature use?

Develop A Feature is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Develop A Feature use?

About 554 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Develop A Feature?

Skills that share tags, products or a category with Develop A Feature: WooCommerce Email Editor Development (woocommerce/woocommerce, 11k stars), React Email (viclafouch/meme-studio, 110 stars), Land TS Mono (UKGovernmentBEIS/inspect_ai, 2.9k stars) and Project (lin-97/gi-demo, 188 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Develop A Feature?

compartmentdev (a GitHub organization) maintains it in compartmentdev/compartment, which has 205 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 20, 2026.

Source: compartmentdev/compartment on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.