pixee organization coding-guidelines
SkillDocs & knowledgeList Pixee organization coding-guidelines documents to discover their filename, status, and size for fix guidance.
Use pixee organization coding-guidelines in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add pixee organization coding-guidelines and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the pixee organization coding-guidelines skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by pixee/pixee-cli in skills/pixee-coding-guidelines/SKILL.md and read by Ahel’s review.
PREREQUISITES: Read
../pixee-shared/SKILL.mdfor global flags, exit codes, and error handling, and../pixee-auth/SKILL.mdif authentication needs to be configured. See../pixee-preferences/SKILL.mdfor the siblingorganization preferencesresource — a freeform markdown blob, distinct from the uploaded documents this skill lists.
Coding-guidelines documents are organization-level files (style guides, security standards,
internal conventions) that the Pixee platform can apply alongside org preferences when
generating fixes. Unlike pixee organization preferences, which manages a single freeform
markdown blob inline, coding-guidelines are a set of uploaded documents, each with its own
filename and processing status.
pixee organization coding-guidelines list
pixee organization coding-guidelines list
No flags beyond the global ones. Pagination is transparent — the CLI walks every page in one call.
Text output is tab-separated with columns display_name, filename, status, size, id.
Use --output json (or --json) for the full HAL record per document.
Examples
# List every coding-guidelines document for the organization
pixee organization coding-guidelines list
# Machine-readable listing piped to jq
pixee organization coding-guidelines list --json | jq '.[] | {display_name, status}'
# Find documents that failed processing
pixee organization coding-guidelines list --json | jq '.[] | select(.status != "ready")'
Best practices
- Check
statusbefore assuming a recently uploaded document is already in effect — processing is asynchronous, and a document in a non-ready state won't yet influence fix generation. - This skill only lists documents; uploading, replacing, or deleting a coding-guidelines document
is done through the Pixee web app or the API directly. See
pixee-apifor the HAL-first discovery pattern if scripting against those endpoints. - Don't conflate this resource with
pixee organization preferences(seepixee-preferences): preferences are one inline markdown blob; coding-guidelines are a set of uploaded documents.
Signals
- GitHub stars
- 31
- Forks
- 12
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
pixee-coding-guidelines- Source
- github.com/pixee/pixee-cli
More in Docs & knowledge
Skill · mattpocock
More in Docs & knowledgecanvas-design
Skill · anthropics
More in Docs & knowledgedoc-coauthoring
Skill · anthropics
More in Docs & knowledgepopups
Skill · coreyhaines31
More in Docs & knowledgewriting-for-agents
Skill · mattpocock
More in Docs & knowledgespec-driven-development
Skill · addyosmani
More in Docs & knowledge