Agentic Coding

Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints.

Security Scan

The skill's requests and runtime instructions are consistent with a contract-first, reviewer-focused coding assistant that stores lightweight state under ~/agentic-coding/ and requires git; nothing requested is disproportionate to the stated purpose.

Purpose & Capability

Name/description (ship production code with contract-driven loops) align with required binary (git) and the instruction set (create diffs, run tests, produce handoffs). Required resources and declared scope are proportional to code-delivery workflows, including Xcode-specific guidance for iOS/macOS work.

Instruction Scope

SKILL.md and companion docs confine reads/writes to ~/agentic-coding/ and the current repository context and explicitly state no undeclared network requests; this is coherent. Note: the skill is instruction-only — the agent executing these instructions could still run repo-local commands (tests, builds) which may have side effects; the docs rely on agent compliance for 'no network' guarantees.

Install Mechanism

No install spec or external downloads — instruction-only skill. This has minimal on-disk footprint (creates files under the user's home path when the user opts in) and raises low installation risk.

Credentials

No environment variables, credentials, or external config paths are requested. The single required binary (git) is appropriate for producing diffs and handoffs; no unrelated secrets or services are required.

Persistence & Privilege

The skill persists its memory and artifacts under ~/agentic-coding/ if the user opts in. always:false (default) and no platform/global config changes are requested. Users should be aware these local files will be created and may contain contract text and validation evidence.

Assessment

This instruction-only skill appears coherent and safe for its stated purpose. Before installing: (1) ensure you are comfortable with the skill creating and reading files under ~/agentic-coding/ (do not put secrets there); (2) confirm git is available and that you are happy for the agent to run repo-local commands and tests (these can have side effects like builds or simulator launches); (3) understand that the SKILL.md claims no undeclared network requests, but that is an operational constraint the agent must follow — monitor initial runs and review the created memory/hand-off files to verify behavior. If you need stricter guarantees, run the skill in a sandboxed repo or review its produced files before merging changes.

Setup

If ~/agentic-coding/ does not exist or is empty, read setup.md, ask a concise kickoff question, and keep any persistence explicitly opt-in.

Positioning

This skill is intentionally different from agentic-engineering and vibe-coding:

• agentic-engineering focuses on multi-agent operating patterns and team throughput.
• vibe-coding focuses on prompt-led exploration and fast idea shipping.
• agentic-coding focuses on contract-first implementation, proof of fix, and reviewer-ready handoff.

When to Use

User needs merge-ready code from an AI agent with explicit quality gates. Use for production features, risky refactors, bug fixes with reproducible failures, and Xcode-centered work such as Swift feature delivery, iOS/macOS regressions, and release-branch hotfixes.

Architecture

Memory lives in ~/agentic-coding/. See memory-template.md for setup.

~/agentic-coding/
|- memory.md       # Persistent preferences and operating mode
|- contracts.md    # Accepted task contracts and non-goals
|- evidence.md     # Test evidence and verification snapshots
`- handoffs.md     # Delivery notes and rollback hints

Quick Reference

Load these files on demand to keep context focused and execution fast.

Topic	File
Setup process	setup.md
Memory template	memory-template.md
PACT loop	protocol.md
Contract prompts	prompt-contracts.md
Merge handoff checklist	handoff.md

Core Rules

1. Lock a Contract Before Writing Code

Start every task with a compact contract:

• Objective: exact outcome in one sentence
• Acceptance: checks that prove success
• Non-goals: what must stay untouched
• Constraints: stack, style, limits, deadlines

No contract, no code.

2. Run the PACT Loop

Use the same execution loop every time:

1. Problem framing: restate objective and assumptions
2. Acceptance design: define checks before edits
3. Change set: produce the smallest useful diff
4. Trace and test: show evidence and residual risk

This skill is execution discipline, not brainstorming. For Xcode workflows, tie acceptance to a concrete target, simulator/device, and test command before editing.

3. Keep Diffs Surgical

One user objective maps to one focused change set:

• Prefer file-local edits over broad rewrites
• Separate behavior change from style cleanup
• Avoid hidden side effects outside declared scope

If scope grows, split into a second contract.

4. Prove Failure Then Prove Fix

For bugs and regressions:

• Capture the failing condition first (test, log, or reproduction)
• Apply minimal fix
• Re-run the same check to prove resolution

Never claim fixed without before and after evidence.

5. Deliver Handoff-Grade Output

End each cycle with a delivery packet:

• What changed and why
• Files touched and blast radius
• Validation run and results
• Known risks and rollback path

If handoff is unclear, the task is not finished.

6. Escalate With a Structured Fallback

When blocked after two failed attempts:

• Stop editing
• State what was tried
• Propose two grounded alternatives
• Request a decision with tradeoffs

Do not keep guessing in loops.

Common Traps

• Starting implementation without acceptance checks -> endless iteration and unclear done state.
• Asking the agent for full rewrites -> noisy diffs and avoidable regressions.
• Mixing feature work with architecture overhaul -> weak reviewability and hard rollback.
• Reporting success without reproducible evidence -> false confidence in production.
• Treating AI output as final draft -> quality debt moved to code review.

Security & Privacy

Data that leaves your machine:

• None from this skill itself

Data that stays local:

• Contracts, evidence notes, and handoff summaries in ~/agentic-coding/

This skill does NOT:

• Trigger undeclared network requests
• Access files outside its own memory path
• Write to global or platform memory stores
• Auto-approve risky code without explicit evidence

Scope

This skill ONLY:

• Improves execution quality of AI-assisted coding
• Enforces contract driven implementation and verification
• Produces clear handoff packets for reviewers

This skill NEVER:

• Replaces security review for high risk domains
• Encourages blind trust in generated code
• Overrides project specific contribution rules

Related Skills

Install with clawhub install <slug> if user confirms:

• agentic-engineering - Multi-agent collaboration and operating patterns.
• coding - General coding support across stacks and tasks.
• code - Broad code authoring and editing assistance.
• copilot - Companion style IDE assistance patterns.
• delegate - Structured task delegation to autonomous agents.

Feedback

• If useful: clawhub star agentic-coding
• Stay updated: clawhub sync