implementing-code
Implement Code Changes With Git Commits
Implementation tasks need consistent edits, commits, and status reporting. This skill guides Claude, Codex, and Claude Code through investigation, code changes, git commits, and completion reports.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "implementing-code" from https://skillstore.io/skills/1gy-implementing-code.md and its manifest at https://skillstore.io/api/skills/1gy-implementing-code/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "implementing-code". Implement a validation fix for empty form names.
Expected outcome:
- Changed files: form validation and related tests.
- Summary: Added an empty-name guard that matches existing validation behavior.
- Commit: fix: validate empty form names.
Using "implementing-code". Add a small settings toggle and commit it.
Expected outcome:
- Changed files: settings view, toggle component, and state handling.
- Summary: Added the requested toggle using the existing settings pattern.
- Commit: feat: add settings toggle.
Security Audit
SafeThe three static findings are false positives caused by Markdown code fences, not Ruby or shell backtick execution. The skill documents limited git add and git commit usage for its implementation workflow. I found no evidence of prompt injection, secret access, network access, or data exfiltration intent.
Risk Factors
⚙️ External commands (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/1gy-implementing-code/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/1gy-implementing-code?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/1gy-implementing-code?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1gy-implementing-code/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/1gy-implementing-code.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
1gy. (2026). implementing-code security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1gy-implementing-code/audits/6BibTeX citation
@techreport{1gy-1gy-implementing-code-2026,
author = {1gy},
title = {implementing-code security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/1gy-implementing-code/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "implementing-code security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "1gy"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/1gy-implementing-code/audits/6"
identifiers:
- type: other
value: "skillstore:1gy-implementing-code:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Ship a Small Feature
Implement a requested feature, follow existing code patterns, and commit the result.
Fix a Production Bug
Investigate related files, apply a focused fix, and create a conventional commit.
Coordinate Parallel Work
Keep implementation work isolated and report file conflicts to a coordinating manager.
Try These Prompts
Implement this requested change: [describe the change]. Follow existing project patterns and commit the completed work.
Investigate and fix this bug: [describe the bug]. Review related files first, then commit the smallest correct fix.
Add this feature: [feature]. Preserve current behavior, follow CLAUDE.md rules, and report changed files and the commit hash.
Implement this scoped task: [task]. Avoid files owned by parallel work, report conflicts immediately, and create a conventional commit.
Best Practices
- Provide a clear purpose and completion criteria before starting implementation.
- Review CLAUDE.md and nearby code before editing files.
- Keep commits focused and use conventional commit messages.
Avoid
- Do not edit files assigned to parallel tasks.
- Do not skip investigation before writing changes.
- Do not create broad commits that mix unrelated work.