agentleFS
Sign inStart free
FreddyPolyFreddyPoly/claude-skills/implement-issue/SKILL.md

implement-issue

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Pick up and implement one unblocked issue from a project's issues/ folder (from doc-to-issues), using the issue file as the source of truth so an agent with no memory of the original interview can still build it correctly. Runs the actual work in a dedicated subagent — same model implement-backlog already uses per issue — so the invoking session's context stays clean and only sees the final summary. Only picks up owner: agent/placeholder issues — owner: user issues (credentials, business decisions only the user can supply) are skipped and listed as waiting-on-you; placeholder issues (colors, copy) are built with a flagged default, swapped in later. Checks for issues stuck in-progress from an interrupted session, and done issues flagged needs-review by a security spec change, before picking new work. Covers selecting the issue, code-quality rules (existing conventions, no premature abstraction, TDD when tested), code-review before marking done (plus security-review when security: true), and updating docs/backlog after. Marks a finished issue done ⚠️ pending-review (rather than plain done) so the optional review-issue skill can later give it an independent second pass — this doesn't block anything downstream, including qc. Use to implement the next issue, work the backlog, or invoke /implement-issue. Requires an issues/ folder — if none, use doc-to-issues first.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-issue, merge-pr and 4 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.
  • sahinSkill

    create-issue

    Also in 6 projects that use this

  • TermiX-officialSkill

    merge-pr

    Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success.

    Also in 3 projects that use this

  • ShopifySkill

    triage-issue

    Triage a GitHub issue — classify priority (P0/P1/P2), search for duplicates, and apply labels.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 5 projects that use this

  • OpenAISkill

    writing-skills

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

23 rules. 0 are common, 11 are distinctive, and 12 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 12

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 29 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.

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