agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-workspace/.claude/skills/implement_direct/SKILL.md

implement-direct

Skill49 starsChanged 2 days agoMITView on GitHub

Implement a small, well-defined issue directly — no planning phase, no task tracker. The user may provide an issue number as the argument (available as $ARGUMENTS). If no issue number is provided: 1. Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line 2. If the file doesn't exist or has no issue number, ask the user 1. Fetch issue details Call mcp__mcp-workspace__github_issue_view with the issue number. Read the issue title, description, and acceptance criteria carefully. Read linked…

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    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:

    If no issue number is provided:

    line 23
  2. Very specific:

    Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line

    line 24
  3. Distinctive:

    If the file doesn't exist or has no issue number, ask the user

    line 25
  4. Very specific:

    Call mcp__mcp-workspace__github_issue_view with the issue number.

    line 30
  5. Distinctive:

    Read the issue title, description, and acceptance criteria carefully.

    line 31
  6. Distinctive:

    Read linked issues first: If the issue points to an epic, design doc, dependencies, or sibling issues, read those before implementing — it …

    line 32
  7. Distinctive:

    If it exits with code 3 (ambiguous), stop: show the candidate branches from its log output and ask the user which branch to use.

    line 38
  8. Distinctive:

    Read relevant source files referenced in the issue

    line 42
  9. Distinctive:

    Follow existing code patterns and conventions

    line 48
  10. Distinctive:

    Keep changes focused and minimal — only what the issue requires

    line 49
  11. Very specific:

    Use mcp__mcp-tools-py__run_format_code to format all code with the project's configured formatter.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Implement Direct

Implement a small, well-defined issue directly — no planning phase, no task tracker.

Resolve Issue Number

The user may provide an issue number as the argument (available as $ARGUMENTS). If no issue number is provided:

  1. Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
  2. If the file doesn't exist or has no issue number, ask the user

Steps

  1. Fetch issue details Call mcp__mcp-workspace__github_issue_view with the issue number. Read the issue title, description, and acceptance criteria carefully. Read linked issues first. If the issue points to an epic, design doc, dependencies, or sibling issues, read those before implementing — it may not be self-contained, and any "read first" note is mandatory.
  2. Checkout/create issue branch
    mcp-coder gh-tool checkout-issue-branch <issue_number>
    If it exits with code 3 (ambiguous), stop: show the candidate branches from its log output and ask the user which branch to use. Do not continue until they answer.
  3. Understand context
    • Read relevant source files referenced in the issue
    • Understand the existing code patterns and conventions
    • Identify the minimal set of changes needed
  4. Implement changes
    • Make the required code changes directly
    • Follow existing code patterns and conventions
    • Keep changes focused and minimal — only what the issue requires
  5. Run quality checks
    • mcp__mcp-tools-py__run_pylint_check — fix all issues
    • mcp__mcp-tools-py__run_pytest_check (with extra_args: ["-n", "auto"]) — fix all failures
    • mcp__mcp-tools-py__run_mypy_check — fix all issues
    • mcp__mcp-tools-py__run_ruff_check — fix all issues
  6. Format code Use mcp__mcp-tools-py__run_format_code to format all code with the project's configured formatter.
  7. Update issue status
    mcp-coder gh-tool set-status status-07:code-review
  8. Suggest follow-up steps
    • /commit_push — commit and push changes
    • /check_branch_status — verify branch is clean
    • /implementation_review — request a review of the implementation

Scope Guidance

This skill is designed for small, well-defined issues that can be implemented in a single pass. If the issue is complex or involves multiple components, recommend the full workflow instead:

  1. /create_plan — create a detailed implementation plan
  2. /implement — implement the plan step by step

Note: This skill has disable-model-invocation — it can only be run by the user typing /implement_direct.

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.