agentsclimarketplace

Continue feature

Skill YoniChechik/claude-code-config/skills/continue-feature

Personal Claude Code configuration (hooks, commands, agents, settings).

Install
npx -y skills add YoniChechik/claude-code-config --skill continue-feature

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Resume work on existing feature clone

SKILL.md

2.6 KB, 593 tokens by cl100k_base, as published. Nobody here has run it

Continues work on an existing feature clone with proper context analysis.

Input from user

"$ARGUMENTS"

Parse this as natural language. Extract:

  1. Feature identifier — branch name, feature description, or PR reference that identifies which feature to continue
  2. PR (optional) — a PR URL or number if mentioned
  3. Next action (optional) — anything that sounds like instructions for what to work on next

If no input at all: "Error: Please describe which feature you want to continue."

If next action is not provided, gather context and state, then proceed based on the natural next step in the workflow.

Process

Step 1a: Search for Existing Clone

List existing clones in _clones/ directory and try to match the feature description:

ls -1 _clones/

If found → Continue to Step 2 (navigate) If not found → Continue to Step 1b (check remote branches)

Step 1b: Check Remote Branches

Check if a remote feature branch exists that matches the description:

git fetch --prune
git branch -r

Review the list of remote branches and match one to the user's feature description.

If found → Run /create-clone with the matched branch name, then continue to Step 4 If not found → Exit with error:

  • Tell user: "Feature branch not found locally or remotely"
  • Suggest: "Use /new-feature <feature-description> to start a new feature"

Step 2: Navigate to Feature Clone

Change to the feature clone directory using /cd-permanent _clones/$FEATURE_NAME skill.

Step 3: Check State

  1. Check git branch state:
bash ~/.claude/scripts/git_branch_state.sh

if not synced with main, run the /sync skill

Step 4: Launch CI Watcher

Run /ci-watcher skill to launch the CI watcher in the background for the current branch.

Step 5: Gather Context & Analyze Status

  1. Use explorer subagent to understand the codebase relevant to the feature
  2. Check if plan-$FEATURE_NAME.md exists — if yes, read it
  3. Run git diff origin/main...HEAD to see what's been done so far
  4. Compare progress against the plan (if exists)
  5. Run the /feature-workflow skill to understand the full workflow when building features

Step 6: Execute Next Action

Proceed immediately without asking for approval. Using all gathered context:

  • What the feature is about (from plan or branch name)
  • What has been done so far (from git diff)
  • Git branch state
  • Where we are in the feature-workflow
  • The user's requested next action

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.