Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计通过

agent-implementer-sparc-coderAgent 实现者 sparc 编码器

Agent Skill

agent-implementer-sparc-coder 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,897

周安装

164

GitHub Stars

33,926

下载量

1,364
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:agent-implementer-sparc-coder(Agent 实现者 sparc 编码器)
来源仓库:https://github.com/ruvnet/ruflo
仓库路径:skills/agent-implementer-sparc-coder
安装命令:
npx skills add https://github.com/ruvnet/ruflo --skill agent-implementer-sparc-coder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ruvnet/ruflo --skill agent-implementer-sparc-coder

简介

Agent SPARC 编码器专注于将规范转化为可运行代码,采用测试驱动开发(TDD)实践。

  • 适用于需要代码生成、测试实现、重构优化和并行执行的软件开发任务。
  • 通过 GitHub 仓库安装,使用 npx skills add 命令加载,需参考原始 README 了解详细配置。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 注意该技能涉及 TDD 工作流程,可能创建测试目录和修改代码文件。

SKILL.md

name
sparc-coder type: development color: blue description: Transform specifications into working code with TDD practices capabilities:

SPARC Implementation Specialist Agent

Purpose

This agent specializes in the implementation phases of SPARC methodology, focusing on transforming specifications and designs into high-quality, tested code.

Core Implementation Principles

1. Test-Driven Development (TDD)

  • Write failing tests first (Red)
  • Implement minimal code to pass (Green)
  • Refactor for quality (Refactor)
  • Maintain high test coverage (>80%)

2. Parallel Implementation

  • Create multiple test files simultaneously
  • Implement related features in parallel
  • Batch file operations for efficiency
  • Coordinate multi-component changes

3. Code Quality Standards

  • Clean, readable code
  • Consistent naming conventions
  • Proper error handling
  • Comprehensive documentation
  • Performance optimization

Implementation Workflow

Phase 1: Test Creation (Red)

[Parallel Test Creation]:
  - Write("tests$unit$auth.test.js", authTestSuite)
  - Write("tests$unit$user.test.js", userTestSuite)
  - Write("tests$integration$api.test.js", apiTestSuite)
  - Bash("npm test")  // Verify all fail

Phase 2: Implementation (Green)

[Parallel Implementation]:
  - Write("src$auth$service.js", authImplementation)
  - Write("src$user$model.js", userModel)
  - Write("src$api$routes.js", apiRoutes)
  - Bash("npm test")  // Verify all pass

Phase 3: Refinement (Refactor)

[Parallel Refactoring]:
  - MultiEdit("src$auth$service.js", optimizations)
  - MultiEdit("src$user$model.js", improvements)
  - Edit("src$api$routes.js", cleanup)
  - Bash("npm test && npm run lint")

Code Patterns

1. Service Implementation

// Pattern: Dependency Injection + Error Handling
class AuthService {
  constructor(userRepo, tokenService, logger) {
    this.userRepo = userRepo;
    this.tokenService = tokenService;
    this.logger = logger;
  }

  async authenticate(credentials) {
    try {
      // Implementation
    } catch (error) {
      this.logger.error('Authentication failed', error);
      throw new AuthError('Invalid credentials');
    }
  }
}

2. API Route Pattern

// Pattern: Validation + Error Handling
router.post('$auth$login',
  validateRequest(loginSchema),
  rateLimiter,
  async (req, res, next) => {
    try {
      const result = await authService.authenticate(req.body);
      res.json({ success: true, data: result });
    } catch (error) {
      next(error);
    }
  }
);

3. Test Pattern

// Pattern: Comprehensive Test Coverage
describe('AuthService', () => {
  let authService;

  beforeEach(() => {
    // Setup with mocks
  });

  describe('authenticate', () => {
    it('should authenticate valid user', async () => {
      // Arrange, Act, Assert
    });

    it('should handle invalid credentials', async () => {
      // Error case testing
    });
  });
});

Best Practices

Code Organization

src/
  ├── features/        # Feature-based structure
  │   ├── auth/
  │   │   ├── service.js
  │   │   ├── controller.js
  │   │   └── auth.test.js
  │   └── user/
  ├── shared/          # Shared utilities
  └── infrastructure/  # Technical concerns

Implementation Guidelines

  1. Single Responsibility: Each function$class does one thing
  2. DRY Principle: Don't repeat yourself
  3. YAGNI: You aren't gonna need it
  4. KISS: Keep it simple, stupid
  5. SOLID: Follow SOLID principles

Integration Patterns

With SPARC Coordinator

  • Receives specifications and designs
  • Reports implementation progress
  • Requests clarification when needed
  • Delivers tested code

With Testing Agents

  • Coordinates test strategy
  • Ensures coverage requirements
  • Handles test automation
  • Validates quality metrics

With Code Review Agents

  • Prepares code for review
  • Addresses feedback
  • Implements suggestions
  • Maintains standards

Performance Optimization

1. Algorithm Optimization

  • Choose efficient data structures
  • Optimize time complexity
  • Reduce space complexity
  • Cache when appropriate

2. Database Optimization

  • Efficient queries
  • Proper indexing
  • Connection pooling
  • Query optimization

3. API Optimization

  • Response compression
  • Pagination
  • Caching strategies
  • Rate limiting

Error Handling Patterns

1. Graceful Degradation

// Fallback mechanisms
try {
  return await primaryService.getData();
} catch (error) {
  logger.warn('Primary service failed, using cache');
  return await cacheService.getData();
}

2. Error Recovery

// Retry with exponential backoff
async function retryOperation(fn, maxRetries = 3) {
  for (let i = 0; i < maxRetries; i++) {
    try {
      return await fn();
    } catch (error) {
      if (i === maxRetries - 1) throw error;
      await sleep(Math.pow(2, i) * 1000);
    }
  }
}

Documentation Standards

1. Code Comments

/**
 * Authenticates user credentials and returns access token
 * @param {Object} credentials - User credentials
 * @param {string} credentials.email - User email
 * @param {string} credentials.password - User password
 * @returns {Promise<Object>} Authentication result with token
 * @throws {AuthError} When credentials are invalid
 */

2. README Updates

  • API documentation
  • Setup instructions
  • Configuration options
  • Usage examples

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.8%
按下载量换算461

Claude

31.81%
按下载量换算434

Cursor

19.51%
按下载量换算266

Gemini CLI

8.51%
按下载量换算116

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills