agentleFS
Sign inStart free
TJaenichenTJaenichen/claude-code-harness/skills/project/starttask/SKILL.md

starttask

Skill0 starsChanged 3 months agoMITView on GitHub

Start a new task - pull main, create worktree and feature branch from DevOps work item

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the work item doesn't exist, report the error clearly

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Start New Task

Work item ID: $ARGUMENTS

Your task

  1. Pull latest main in C:\work\Payments:
    cd /c/work/Payments && git checkout main && git pull
  2. Fetch work item details from DevOps:
    curl -L --negotiate -u : "https://devops.example.com/DefaultCollection/MyProject/_apis/wit/workitems/$ARGUMENTS?api-version=6.0"
  3. Extract the title from fields.System.Title and create a short name:
    • Remove special characters
    • Replace spaces with underscores
    • Truncate to max 15 characters
    • Example: "Add Widget Support for New Processor" → "AddWidgetSup"

  4. Create worktree and branch (from C:\work\Payments):

    git worktree add -b feature/<ID>_<ShortName> /c/work/<ID>_<ShortName> origin/main

    Where:

    • Branch name: feature/$ARGUMENTS_<ShortName>
    • Directory: /c/work/$ARGUMENTS_<ShortName> (no "feature-" prefix to keep path short)
  5. Push the feature branch to create remote tracking:
    cd /c/work/<ID>_<ShortName>
git push -u origin feature/<ID>_<ShortName>
  6. Report success with:
    • Work item title
    • Branch name
    • Worktree path
    • Conversation renamed to

Important

  • Directory name does NOT include "feature-" prefix (to avoid Windows path length issues)
  • Branch name DOES include "feature/" prefix
  • Short name must be max 15 characters to avoid path-too-long errors on Windows
  • If the work item doesn't exist, report the error clearly

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free