bitsocialnet/issue-format
.codex/skills/issue-format/SKILL.md
Formats GitHub issue titles and descriptions for tracking problems that were fixed. Use when proposing or implementing code changes, creating GitHub issues, or when the user asks for issue suggestions.
$ install --global
skillsauthnpx skillsauth add bitsocialnet/bitsocial-web issue-formatInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:35 PM255.0s1 file scanned
SKILL.md
- name:
- issue-format
- description:
- Formats GitHub issue titles and descriptions for tracking problems that were fixed. Use when proposing or implementing code changes, creating GitHub issues, or when the user asks for issue suggestions.
Issue Format
Template (copy this structure exactly)
Raw markdown:
> **GitHub issue:**
> - **Title:** `Short issue title here`
> - **Description:** Description sentence one. Sentence two with `codeRef()` references.
Rules
- Use markdown blockquote (
>prefix) — no exceptions - Title goes after
**Title:**wrapped in exactly ONE backtick pair - NEVER put backticks inside the title — the whole title is one code span, no nesting
- Description uses backticks for code references — title does NOT
- Title: as short as possible
- Description: 2-3 sentences about the problem (not the solution), present tense
Wrong vs Right
❌ WRONG — missing backticks around title:
> - **Title:** Mod queue should use /modqueue instead of /queue
❌ WRONG — backticks around individual words instead of whole title:
> - **Title:** Mod queue should use `/modqueue` instead of `/queue`
✅ CORRECT — entire title in one backtick pair, no backticks inside:
> - **Title:** `Mod queue should use /modqueue instead of /queue`
Self-check
Before outputting, verify:
- [ ] Lines start with
> - [ ] Title is wrapped in exactly one backtick pair:
`like this` - [ ] No backticks inside the title text
- [ ] Code references in description (not title) use backticks
Related Skills
bitsocialnet/vercel-react-best-practices
development
VerifiedTrustedCommunity
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
1SKILL.mdUpdated Apr 16, 2026
bitsocialnet/translate
data-ai
VerifiedTrustedCommunity
Add or update i18next translation keys across all language files by spawning translator subagents. Use when the user asks to add a new translation, update existing translations, translate text, or work with i18n keys. Triggers on "translate", "add translation", "translation key", "i18n", "localization".
1SKILL.mdUpdated Apr 16, 2026
bitsocialnet/test-apk
development
VerifiedTrustedCommunity
Test and debug Android wrapper features for Bitsocial Web using a local Android emulator or attached device. Manages emulator lifecycle, builds and installs the wrapper when commands are provided, runs focused checks, captures logcat diagnostics, and debugs WebView or TWA behavior. Use when the user asks to test Android, debug WebView behavior, run emulator tests, or says "test-apk".
1SKILL.mdUpdated Apr 16, 2026
bitsocialnet/review-and-merge-pr
testing
VerifiedTrustedCommunity
Review an open GitHub pull request, inspect bot and human feedback, decide which findings are valid, implement fixes on the PR branch, and merge the PR into master when it is ready. Use when the user says "check the PR", "address review comments", "review PR feedback", or "merge this PR".
1SKILL.mdUpdated Apr 16, 2026