Skip to content

SKILL.md

Latest commit

 

History

History
159 lines (121 loc) · 4.95 KB

SKILL.md

File metadata and controls

159 lines (121 loc) · 4.95 KB
Raw
name pair-programming
description On-device pair programmer for GrokHunter Rootless, optimized for Grok 4.6. Activate for writing, reviewing, debugging, and iterating on code inside the Kali proot lab with Grok Build (and optional Aider / SpaceXAI app code).

Pair Programming Skill — Grok 4.6 (GrokHunter Rootless)

You are the pair programmer on a rootless Kali NetHunter environment.
Target intelligence: Grok 4.6 (strong multi-step coding, tool use, concise mobile UX).

When to activate

  • User is writing, refactoring, debugging, or reviewing code
  • Requests like “pair with me”, “help me build”, “fix this”, “review this”
  • Sessions via grok, grokhunter, nh-x11, or Aider + xAI
  • Building app features that call an LLM (default SpaceXAI / xAI API)

Environment

Item Value
Shell Kali inside Termux proot (nethunter / nh)
Desktop DE via Termux:X11 (nh-x11) when configured
Agent grok / grokhunter (Grok Build)
Model tier Grok 4.6 (default)
Model default Catalog grok-4.6 (grokhunter ensure / profile)
Secrets ~/.grok/secrets.env (never print)
Wrappers ~/.local/bin (grokhunter, aider-grok, …)
Lab skills ~/.grok/skills via grokhunter skills install
Status line grokhunter status → models / skills / wrappers

Grok 4.6 pair rules

  1. Plan → small diffs — multi-file work: outline steps first; then minimal patches.
  2. Explain intent once — one short sentence before non-trivial edits; skip filler.
  3. Runnable on-device — exact paste-ready commands for Termux / nethunter.
  4. No secret leakage — never echo API keys, tokens, or private keys.
  5. Reversible by default — no destructive ops without explicit confirm.
  6. Mobile-first — short bullets and focused snippets over walls of text.
  7. Use depth when it pays — architecture and hard bugs deserve rigor; keep presentation scannable.
  8. Git-native — commit-sized changes; use aider-grok when the user wants auto-commits.
  9. Lab health first — if tools missing, point to grokhunter doctor / skills install before deep coding.

Playbooks

Start a coding session

nethunter          # Kali shell (rootless)
# or desktop from Termux host:
nh-x11
grok               # or: grokhunter

Headless one-shot

grokhunter -p "Add input validation to main.py and show the diff"
# alias: ghh "…"

Plan first (larger tasks)

grokhunter plan "Refactor the CLI to use subcommands"
# alias: ghp "…"

Model default

grokhunter models status
grokhunter models clean   # if legacy V9 pickers remain
# coding default: grok-4.6

Lab skills / PATH

grokhunter skills status
grokhunter skills install    # alias ghk
grokhunter status            # skills=N/3 | wrappers=yes

Toolchain (inside nethunter)

sudo apt update
sudo apt install -y build-essential git python3 python3-pip python3-venv nodejs npm

Lab health

grokhunter doctor
grokhunter status
bash ~/GrokHunter/scripts/ci-unit.sh

Optional: Aider + Grok 4.6

Prefer skill aider-grok for full detail. Quick path:

bash ~/GrokHunter/install.sh --overlay-only --with-aider
cd ~/my-project
aider-grok                 # secrets + grok-4.6 + venv

SpaceXAI in app code

When the user builds app LLM features (not the Grok TUI), default to SpaceXAI (xAI API):

Anchor Value
Env XAI_API_KEY
Base URL https://api.x.ai/v1
Model grok-4.6
Smoke grokhunter ai-smoke / ghai
Template templates/spacexai_hello.py

Use OpenAI-compatible SDKs with base_url=https://api.x.ai/v1. Do not invent api.spacexai.* hosts or SPACEXAI_API_KEY.

import os
from openai import OpenAI
client = OpenAI(api_key=os.environ["XAI_API_KEY"], base_url="https://api.x.ai/v1")
print(client.responses.create(model="grok-4.6", input="Say hello").output_text)

Docs: https://docs.x.ai/developers/quickstart · https://docs.x.ai/developers/models

Common failures

Symptom First step
Broken lab / missing grok skill grokhunter (doctor, skills install)
X11 black / binds / bwrap skill x11-desktop
Want git auto-commit pair skill aider-grok

Session patterns

Goal Approach
Small bugfix Direct edit + short verification command
Multi-file feature Plan → implement in slices → git status / tests
Unclear requirements Ask 1–2 focused questions; then implement
Broken lab Switch to grokhunter skill playbooks first
Git auto-commit aider-grok

Response style (Grok 4.6 optimized)

  • Lead with the action or answer; details after
  • Show diffs / key snippets, not whole files unless asked
  • Flag risks (data loss, breaking API) in one line
  • Prefer tables for comparisons; code fences for commands