agentleFS
Sign inStart free
albertomartureloalbertomarturelo/sii/.agents/skills/issue-start/SKILL.md

issue-start

Skill18 starsChanged 17 days agoMITView on GitHub

Pick up a GitHub issue as the focus of this session: fetch it, load its ADRs and one reference file, create the branch, and state the objective + acceptance checklist. Invoke explicitly with an issue number.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. apokamo/kaji★ 16same name
    2. gihwan-dev/claude-code-gui★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: "Ready to start?"

    line 44
  2. Very specific:

    If Estimated sessions > 1, remind the user the issue should have been decomposed and ask whether to split it now via /issue-new.

    line 46
  3. Distinctive:

    Token discipline: do NOT scan target files or neighboring modules at this step.

    line 49

≈ “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

The user passes an issue number. If they don't, ask which (or list open issues via gh issue list --repo albertomarturelo/sii --state open).

  1. Fetch the issue: gh issue view <n> --repo albertomarturelo/sii
  2. Parse the 6 fixed sections: Context, Target, ADRs to load, Acceptance criteria, Reproduction (fixes only), Estimated sessions. If any required section is missing, STOP and tell the user the issue is malformed — propose editing it before starting. Don't infer.
  3. For each ADR listed in ADRs to load, read the file in docs/decisions/. These set the constraints the implementation must satisfy.
  4. Read the file in Pattern to mirror ONCE for shape. Skim, don't study.
  5. Do NOT read the files listed in Target yet — they are where the work goes, not where context comes from.
  6. Create the branch: git switch -c <type>/GH-<n>-<slug> where <type> matches the issue's type label and <slug> is a short kebab-case summary.
  7. Summarize for the user, exactly:
    • Objective (one line, from Context).
    • Acceptance checklist (verbatim — this is the DoD; copy to the PR description on submit).
    • ADRs loaded and what each constrains.
    • Target paths (the files you'll write to).
    • Pattern to mirror.
    • Branch created: <type>/GH-<n>-<slug>.
  8. Ask: "Ready to start?"

If Estimated sessions > 1, remind the user the issue should have been decomposed and ask whether to split it now via /issue-new.

Token discipline: do NOT scan target files or neighboring modules at this step. The issue body + ADRs are the spec. Code reading happens when implementation starts, not during orientation.

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