Github Conventions
GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.
Install
$ agentstack add skill-jartan-llc-grimoire-github-conventions ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jartan-llc-grimoire-github-conventions) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
GitHub Conventions
CRITICAL: # auto-links to issues/PRs on GitHub. Use 1./2./3. for numbered lists and "Finding 1:"/"Item 1:" for labeled items -- never #1, #2, #3 as markers.
Authentication
Never reconfigure auth transport to unblock a command. Don't switch the remote between SSH and HTTPS, add a credential helper, or push to an explicit URL. A missing key or token scope is a missing credential, not a transport problem -- only the user can supply it, and working around it changes config they never asked you to touch, often globally. Stop and ask.
Branches
Feature branches: feature/ or feature/issue- Always check if a branch already exists for an issue before creating a new one.
For sub-issues of a larger feature, branch from the parent feature branch rather than main. Sub-issue work merges back into the parent feature branch, which eventually merges to main.
Commits
Conventional commits format: : description
Types: feat:, fix:, docs:, style:, refactor:, test:, chore: Optional scope: feat(frontend): description
Issues
Templates in .github/ISSUE_TEMPLATE/ -- read them for section structure.
- Bug reports: must have label
bug - Feature requests: must have label
enhancement
Pull Requests
PR template at .github/PULL_REQUEST_TEMPLATE.md -- read it for section structure. Use Closes # to link PRs to issues.
Code Reviews
Reviews are posted as PR comments. See [review-format.md](review-format.md) for the recommended structure -- severity buckets and the #N footgun to avoid in the summary.
Implementation Plans
Plans are posted as issue comments and saved to .claude/workspace/. See [plan-format.md](plan-format.md) for the recommended structure.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jartan-LLC
- Source: Jartan-LLC/grimoire
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.