agentleFS
WeaverseWeaverse/.agents/skills/work/SKILL.md

work

Skill0 starsChanged 6 days agoMITView on GitHub

Start issue-governed Weaverse implementation using the repository's branch policy and one flat spec. Use when explicitly asked to pick up an issue; not for review, verification or release support on existing work.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use authoring, done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • automagik-devSkill

    authoring

    Write or revise a Genie skill so it survives the shipped contract — frontmatter, house size, starter card, and runtime-neutral voice.

    Also in 3 projects that use this

  • robzolkosSkill

    done

    Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.

    Also in 3 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 4 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • MicrosoftSkill

    merge

    Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read repository instructions and the requested issue, including its discussion and existing Development links.

    line 10
  2. Distinctive:

    If no issue is named, search related open and closed Weaverse issues and read likely matches before choosing.

    line 11
  3. Distinctive:

    Follow the repository's branching policy.

    line 14
  4. Very specific:

    Search for the closest canonical spec before creating one.

    line 17
  5. Very specific:

    Keep the original creation-date path when updating.

    line 19
  6. Distinctive:

    No feature/month folder, per-spec README, parallel plan, work-log or handoff file unless requested.

    line 30
  7. Very specific:

    Commit, push, publish a PR or update project metadata only within the requested authority.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “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

Work from an issue

  1. Read repository instructions and the requested issue, including its discussion and existing Development links. If no issue is named, search related open and closed Weaverse issues and read likely matches before choosing. Reuse a genuine match; creating, reopening or changing an issue is a separate authorized external write.
  2. Resolve the actual PR base and remote default separately. Preserve the current owner's branch and dirty work. Follow the repository's branching policy; do not assume main, change branches under active work, or stash to inspect.
  3. For new substantive implementation, verify the matching issue before changing source. Small clear fixes can use the issue as the mini-spec. Support on an existing PR reuses its issue/spec without extra tracking documents.
  4. Search for the closest canonical spec before creating one. Use one flat YYYY-MM-DD-what-update.md directly in the repository's existing spec root (.specs/ or .weaverse/specs/, per the team rule). Keep the original creation-date path when updating. Include the exact issue URL or Weaverse/repo#number.
  5. The single file contains these sections, without duplicating the issue's owner, status or priority:

    ## Outcome
    ## Scope and non-goals
    ## Acceptance
    ## Approach
    ## Verification

    No feature/month folder, per-spec README, parallel plan, work-log or handoff file unless requested. Link one shared contract across repositories instead of copying it. Leave unrelated legacy specs alone; consolidate a legacy outcome only when substantively editing it, preserving history and backlinks.

  6. Implement within the agreed scope and run the repository's gates. Include required version/changelog changes in this implementation before final review and CI, never in a later version-only preparation branch.
  7. Commit, push, publish a PR or update project metadata only within the requested authority. A spec-only PR references the issue without Closes #n. Only a default-target PR fully resolving the issue uses a closing keyword. A legitimate non-default target needs a supported explicit Development link, verified by readback; never retarget or close a broader issue merely to satisfy tracking.

Report issue, branch/base, spec path (or issue-as-spec), actual checks and remaining work. Evidence belongs in the existing PR; no new handoff document is needed.

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.