// GitHub workflow conventions for ADAMANT project including issue titles, labels, PR format, and org-wide governance. Use when creating issues, PRs, or managing project workflow.
iOS platform rules, Swift conventions, dependency injection patterns, and code quality standards for ADAMANT iOS. Use when writing or reviewing code.
Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation.
Expert knowledge of ADAMANT iOS app architecture, modules, runtime flow, and system organization. Use when exploring codebase structure, understanding dependencies, or planning architectural changes.
Testing and validation requirements for ADAMANT iOS. Use when writing tests, validating changes, or ensuring code quality before commits.
| name | github-workflow |
| description | GitHub workflow conventions for ADAMANT project including issue titles, labels, PR format, and org-wide governance. Use when creating issues, PRs, or managing project workflow. |
| license | Apache-2.0 |
| compatibility | ADAMANT GitHub organization workflow |
| metadata | {"project":"adamant-ios","domain":"process"} |
Organization-wide conventions for issues, labels, and pull requests in ADAMANT projects.
Follow the organization-wide conventions:
labels.json)Use one or two prefixes maximum.
[Bug] — bugs, crashes, unexpected behavior[Feat] — new functionality[Enhancement] — improvements of existing features[Refactor] — refactoring without intended behavior changes[Docs] — documentation updates[Test] — test additions or improvements[Chore] — routine maintenance (dependencies, CI/CD, tooling)[Task] — general task (including non-coding tasks)[Composite] — multi-part task with sub-tasks[UX/UI] — interface and user experience changesUsually better in Discussions than Issues:
[Proposal], [Idea], [Discussion]labels.json in Adamant-im/.github is the source of truth for label names, casing, descriptions, and colorsbug, enhancement, documentation, etc.)Security, Privacy, UX/UI, Task, Composite task, etc.)For most issues, apply a small but informative set:
bug, enhancement, Task, Composite taskiOS, Swift, Wallets, Messaging, Security, Privacy, Nodes, etc.High priority when neededDo not use legacy status labels for workflow tracking (s/ ...); project/Kanban state is managed in GitHub Projects.
Description, Related issue, How to test, Checklist, etc.Closes #<id>Type: Short summary
Docs: Update AGENTS.md, Fix: Handle nil transaction status, Feat: Add Litecoin wallet[Docs], [Bug], etc. are for Issues)Docs:, Fix:, Feat:, Refactor:, Test:, Chore:When working with GitHub CLI (gh) or other command-line tools that require long text inputs:
.ai/temp/ directory for temporary markdown files (issue descriptions, PR descriptions, etc.).ai/temp/pr-description.md and use gh pr create --body-file .ai/temp/pr-description.mdActivate this skill when: