Agent skill
snakepolish
Implementation phase for stinkysnake workflow. Use when tests are written and plan is ready. Implements functions following the modernization plan, runs tests until passing.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/snakepolish
SKILL.md
Snake Polish - Implementation Phase
Execute the implementation plan from /stinkysnake Phase 9. Implement functions following the modernization plan, run tests iteratively until all pass.
Arguments
$ARGUMENTS
Prerequisites
Before invoking this skill, ensure:
/stinkysnakephases 1-8 completed- Modernization plan reviewed and refined
- Interfaces designed and documented
- Failing tests written by
python-pytest-architect
Instructions
Step 1: Load Context
Read the stinkysnake plan artifacts:
ARTIFACTS TO LOAD:
- [ ] Modernization plan (Phase 3 output)
- [ ] Plan review feedback (Phase 4-5 output)
- [ ] Interface definitions (Phase 7 output)
- [ ] Failing test files (Phase 8 output)
Step 2: Verify Test Baseline
Run tests to confirm failing state:
uv run pytest $ARGUMENTS -v --tb=short 2>&1 | head -100
Expected: Tests fail because implementations don't exist yet.
If tests pass: Stop. Implementation already complete or tests are not testing the right things.
Step 3: Implementation Order
Follow this implementation sequence:
IMPLEMENTATION ORDER:
1. Type definitions (TypeAlias, TypedDict, Protocol)
2. Data structures (dataclass, Pydantic models)
3. Utility functions (pure functions, no side effects)
4. Core business logic
5. Integration points (API clients, file I/O)
6. Entry points (CLI commands, handlers)
Step 4: Implement Following Plan
For each planned change:
FOR EACH IMPLEMENTATION ITEM:
1. Read the interface/protocol definition
2. Read the failing test(s) for this component
3. Implement the function/class
4. Run targeted tests: uv run pytest -k "test_name" -v
5. If fails: debug and fix
6. If passes: move to next item
Step 5: Modern Python Patterns
Apply these patterns during implementation:
Type Annotations
# Use modern union syntax
def process(data: str | None) -> dict[str, Any]:
...
# Use TypeGuard for narrowing
def is_valid_user(obj: object) -> TypeGuard[User]:
return isinstance(obj, dict) and "id" in obj
Protocol-Based Design
from typing import Protocol
class Serializable(Protocol):
def to_dict(self) -> dict[str, Any]: ...
def save(item: Serializable) -> None:
data = item.to_dict()
...
Dataclass Patterns
from dataclasses import dataclass, field
@dataclass(slots=True, frozen=True)
class Config:
name: str
options: list[str] = field(default_factory=list)
Pydantic for Validation
from pydantic import BaseModel, Field
class APIResponse(BaseModel):
status: int = Field(ge=100, le=599)
data: dict[str, Any]
model_config = {"strict": True}
Modern Libraries
# httpx for async HTTP
async with httpx.AsyncClient() as client:
response = await client.get(url)
# orjson for fast JSON
data = orjson.loads(response.content)
output = orjson.dumps(result, option=orjson.OPT_INDENT_2)
# tomlkit for TOML with comments preserved
doc = tomlkit.parse(content)
doc["section"]["key"] = value
Step 6: Iterative Test Loop
After each implementation batch:
# Run full test suite
uv run pytest $ARGUMENTS -v --tb=short
# If failures remain, focus on failing tests
uv run pytest $ARGUMENTS -v --tb=long -x # Stop on first failure
Step 7: Static Analysis Verification
Before completion, verify code quality:
# Format check
uv run ruff format --check $ARGUMENTS
# Lint check
uv run ruff check $ARGUMENTS
# Type check
uv run mypy $ARGUMENTS --strict
Fix any issues that arise.
Step 8: Final Test Run
Confirm all tests pass:
uv run pytest $ARGUMENTS -v --cov --cov-report=term-missing
Success Criteria:
- All tests pass
- No type errors
- No lint errors
- Coverage meets project threshold (typically 80%+)
Completion
When all tests pass and static analysis is clean:
- Report implementation summary
- List any deferred items or technical debt
- Reference documentation updates needed (from Phase 6)
Error Handling
Test Failures That Indicate Test Bugs
If a test failure appears to be a test bug rather than implementation bug:
- Document the suspected test issue
- Check the test against the interface specification
- If test is wrong: fix the test, document the fix
- If unclear: flag for review, continue with other implementations
Blocked Implementations
If an implementation is blocked:
- Document the blocker
- Check if it's a dependency ordering issue
- If external dependency: note and continue with independent items
- If architectural issue: flag for plan revision
References
- stinkysnake skill - Parent workflow
- python-cli-architect agent - Implementation agent
- python3-development skill - Modern Python patterns
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?