doompi-development
/doompi-development
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request.
Original author description
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request.
How it works
- Before changing code
- Implement
- Verify
SKILL.md preview
--- name: doompi-development description: Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request. --- # Scoped Development Deliver the smallest coherent change that satisfies the request and fits the repository. ## Before changing code - Read the applicable repository instructions and inspect the current worktree. - Identify the requested behavior, acceptance evidence, and files that own the behavior. - Reuse nearby patterns and public interfaces before adding a new abstraction. - Ask only when a missing product or architecture choice would materially change the result. ## Implement - Keep edits within the requested scope and preserve unrelated user changes. - Follow existing naming, dependency, error-handling, and testing conventions. - Update tests or documentation only when the behavior change requires them. - Treat generated files, migrations, dependency changes, and external writes as separate actions that need clear authorization. ## Verify - Run the narrowest relevant checks first, then the repository-required lint, typecheck, build, and test commands. - Inspect failures instead of hiding, weakening, or bypassing them. - Report which behavior was verified, which commands ran, and any remaining uncertainty. Do not create branches, commits, releases, or pull requests unless the user requests them.
Versions
The database has no other skills named doompi-development.
Database snapshot: 13.11.2026 · package version e0185cf7a565 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90doompi-review
Review a code change for concrete defects, regressions, missing tests, and contract violations. Use when the user asks for code review, diff review, or risk assessment, not as a general implementation workflow. - 90doompi-testing
Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request. - 90code-review
Review repository changes for correctness, type boundaries, structural quality, and meaningful test coverage. Use for read-only code or PR assessments and development-task readiness checks. - 90reviews
Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change". - 90e2e-verify
Run end-to-end PR verification with browser testing. Use before merge or in fix-and-ship mode when the user asks to verify a PR, run E2E, browser-test, or visually check UI changes. SKIP backend-only checks with no browser/UI path; use review-deep or ship as appropriate. - 100tdd
Implement changes using Test-Driven Development (Red-Green-Refactor). Use for code changes that need coverage or requested test-value audits.